• 1 Post
  • 14 Comments
Joined 1 year ago
Cake day: June 13th, 2023
  • MrOtherGuy@lemmy.worldtoFirefox@lemmy.ml•Transparent page background without affecting content
    0·
    2 days ago

    Right, background-color is not an inherited property (compared to for example color (color of text) which is). But even if it were, inheritance is not “enforced” so if website css sets a backround-color specifically for that element then the inherited value would be lost anyway.

    But the way you now describe it doesn’t seem possible. There is not syntax to apply style rule to “just the innermost element”. I think the closest would be to have everything else have fully transparent background, but the html root element have only partial transparency:

    *{
  background: transparent !important;
}
html:root{
  background: #00000080 !important;
}

    However, you will still face a problem; many websites draw graphics or images as a background-image so if you use the background shorthand property then those graphics will be effectively removed. On the other hand, if you instead set just background-color then parts might get opaque again because a website could be drawing even opaque backgrounds as background-image instead of background-color.

  • MrOtherGuy@lemmy.worldtoFirefox@lemmy.ml•Transparent page background without affecting content
    0·
    2 days ago

    I think the answer depends on which elements exactly you want to make transparent. The page is a layered structure. The html root element is behind them all. Then body element is on top of that, the rest of the elements on top of body, etc.

    So if you intend to have transparency all the way down, then you need to make sure that all the elements in that stack are transparent. If any single item in a stack has an opaque background then the transparency effect stops at that.

    As an example, if you set background:transparent to just body but not the document root element, then body will indeed be transparent, but it does not matter because the root will still be opaque. Likewise, if root is made transparent, but there is any opaque layer on top of that, then only the parts of the root element that are not covered by that opaque layer will show up as transparent. If you have a glass table and put a sheet of paper on top of it, then you don’t see through the part covered by the paper even though the table itself is transparent.

  • MrOtherGuy@lemmy.worldtoFirefox@lemmy.ml•Transparent page background without affecting content
    0·
    2 days ago

    I don’t think I understand exactly what parts you want to make transparent, but this does work:

    1. set browser.tabs.allow_transparent_browser to true
    2. in userChrome.css add #main-window, #tabbrowser-tabpanels{ background: transparent !important; }
    3. in userContent.css add html:root{ background-color: transparent !important; }

    The above would make window background, and the are behind web-content transparent as well as background of html documents - otherwise the background of browser area wouldn’t show up anyway. Toolbars that have their own specified colors would still be colored - which might be opaque or not depending what theme you have selected.

  • MrOtherGuy@lemmy.worldtoFirefox@lemmy.ml•Bookmark list closes
    0·
    13 days ago

    Would be pretty idiotic to not close it, otherwise opening a bookmark would always require a second click to close the popup.

    Anyways, you can go to about:config and set browser.bookmarks.openInTabClosesMenu to false - afterwards you can hold Ctrl (or just click the middle mouse button) while clicking a bookmark from such popup and the popup should stay open.

  • MrOtherGuy@lemmy.worldtoFirefox@lemmy.ml•Is "copy link without tracking" working for you?
    0·
    2 months ago

    That feature removes parameters that are known to be used for tracking. It does not remove all query parameters willy-nilly. For example on youtube it should remove si, feature and kw parameters as well as a set of parameters on a list that applies to all websites. However, pp parameter is not in that to-be-removed list.

    As an example v parameter is for video id on youtube, it would be kinda silly if that was removed, so the feature kinda has to do some site specific action.

  • MrOtherGuy@lemmy.worldtoFirefox@lemmy.ml•PWAs on Android?
    0·
    10 months ago

    If a website has a compatible PWA manifest the there will be an item labelled “install” in the three-dot menu of Firefox in place of usual “add to homescreen” item.

    Edit: There’s a few other requirements as well for the website to be considered installable as PWA, such as it must have a registered service worker so it can work offline. But regardless, if the website provides all the requirements then it can just be installed straight from the menu.