[–] 1 point 2 weeks ago (1 child)

Umm, yeah the library window and sidebar don't really play super well here. One thing that would sort of work for them though is to simply add the filter to the whole library tree, not only the icons - like this here

The problem with this though is that it only sort of works if you remove all the tree indentation, because if we do so, then we can create an svg filter that applies the filter effect only at certain slice of the elements width. So it's really only a solution if you don't need the tree visualization.

  • source
  • parent
  • context
  • [–] 1 point 3 weeks ago (3 children)

    I can't think of a way to exclude internal bookmark items, but what you could do is to keep using the filter that you have, but set the internal icon to black:

    .bookmark-item:not([container]){
      fill: black !important;
    }
    
  • source
  • parent
  • context
  • [–] 3 points 1 month ago (4 children)

    I don't really know what that blue circled space is about - if you can't remove it then I don't think it's a flexible space. Perhaps it's margin created by whatever that "Firefox icon" button next to it is?

    But maybe this style fits the bill to create separate "block" for vertical tabs area?

  • source
  • [–] 1 point 2 months ago (1 child)

    So, the bug that caused this is bug 2058134. The change that was made there is rather inconvenient for user styling, because now the text painting code simply looks if author styles (e.g the web page author) change the selection color and only then use the css specified colors. I'm pretty sure that means that ::selection does absolutely nothing when used in user{Chrome/Content}.css files because they are user, not author styles.

    If you want this changed then you should create a new bug and mark it as being regressed by the above bug.

  • source
  • [–] 1 point 4 months ago* (1 child)
    div.text-container { padding-block: var(--uc-container-block-padding, initial) !important }
    

    Sure, if padding-block isn't set then initial should be alright. I'm guessing the initial value would be 0px so it's probably ok to not set any fallback value.

    But there's actually a rather recent value that you could use in place of initial - that is revert-rule. Whereas initial makes the property use it's "browser default" value, using revert-rule as a fallback makes it use whatever it would have been without that custom style rule - so it would in this case revert to calc((var(--message-bar-container-min-height) - 1lh) / 2).

  • source
  • parent
  • context
  • [–] 2 points 4 months ago (3 children)

    Similar to ::part, the :host selector is not usable from within userChrome.css. So I guess the only way here would be to make the things inside the shadow-root inherit some variables and use those:

    .infobar{
      --uc-container-block-padding: 0px;
      --uc-close-button-block-margin: 0px;
    }
    moz-button.close{ margin-block: var(--uc-close-button-block-margin, 4px) !important }
    div.container { padding-block: var(--uc-container-block-padding, 3px) !important }
    

    This is a bit unfortunate complication, that could in theory break a bit if eg. eg.container elements would ever be outside of .infobar (which I don't think is currently the case). But otherwise it should work just fine.

  • source
  • [–] 1 point 5 months ago (1 child)

    The flex value is a "factor" in a sense that it governs how much the available space is distributed for each element in a container. In the library toolbar there is normally only one item with flex - the spacer. In that case it doesn't matter how large its flex factor is, because every non-zero number is "all there is". If the filter input-box gets flex of 1 then the available space gets distributed evenly for the input-box and the spacer because now they both have flex factor of 1. But if the input-box has flex factor of 1000, then 1000/1001 of the space is distributed for input-box and only 1/1001 for the spacer, effectively making it so that the spacer shouldn't appear to grow at all - not until the input-box reaches its maximum width if it has any.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (3 children)

    In the Library, is it possible to reduce the space between the toolbar

    I think what you want to do for the Library toolbar is to make the search input box flex more that the spacer space:

    #searchFilter{ flex: 1000 !important }
    

    However, the Library’s tooltips still have a border. Is it possible to remove it?

    You can, but not by using userChrome.css. Tooltips in Linbrary window, as well as some within main browser window are using native anonymous content which userChrome.css doesn't apply to. You need to have some way to load a style sheet as user agent sheet - which is only really possible by building Firefox yourself or injecting the style using autoconfig feature.

  • source
  • parent
  • context
  • [–] 1 point 5 months ago (5 children)

    Like this maybe? Setting short duration should be safe so that if there is logic that waits for animation to end then this (probably) won't break it:

    :is(#downloads-indicator-start-box, #downloads-indicator-finish-box) > .toolbarbutton-animatable-image{
      animation-duration: 1ms !important;
    } 
    
  • source
  • [–] 2 points 5 months ago (2 children)

    Something simple like just .tab-stack{ transform: scale(1.2) } might work mostly fine. But I think it might lead to some small overflow problems. Alternatively you could try this:

    #tabbrowser-tabs[orient="vertical"]{
      --uc-tab-icon-size: 24px; /* modify this to change tab icon size */
      --tab-min-height: max(calc(24px + (var(--uc-tab-icon-size) - 16px)),calc(1.7 * 1em));
    }
    #tabbrowser-tabs[orient="vertical"]:not([expanded]) .tab-background{
      margin-inline: auto !important;
      width: calc(var(--tab-min-height) + 2px) !important;
      aspect-ratio: 1;
    }
    .tab-icon-image{
      width: var(--uc-tab-icon-size) !important;
      height: var(--uc-tab-icon-size) !important;
    }
    #tabbrowser-tabs[orient="vertical"]:not([expanded]) .tab-content{
      padding-inline: 0 !important;
      margin-inline: auto;
    }
    #tabbrowser-tabs[orient="vertical"]:not([expanded]) .tab-close-button{
      inset-inline-start: calc(16px - var(--uc-tab-icon-size)) !important;
    }
    

    The tab scrollbar you can probably make bigger simply like this:

    #tabbrowser-arrowscrollbox[orient="vertical"]{
      --uc-scrollbar-width: auto;
    }
    scrollbox[orient="vertical"]{
      scrollbar-width: var(--uc-scrollbar-width) !important;
    }
    
  • source
  •  

    Hi! Just FYI folks, the plan going forward would be to build this community on Fedia instead: Right here https://fedia.io/m/FirefoxCSS

    Thanks to federation, you can also participate in the community through lemmy if you want - though some features such as microblog or sidebar info won't be accessible via lemmy - for now at least. The link to access the community via lemmy world would be https://lemmy.world/c/FirefoxCSS@fedia.io

    See ya there!

     

    Let's have this post here also...

    As a part of the front-end technical modernization the old xul box model is being replaced with modern flexbox all around the UI. Relevant bug 1820534

    Previously, just about everything used display: -moz-box but in Firefox 113 the default display model was changed to modern display: flex instead.

    What this means first-hand is that all legacy box model -related properties will not do anything anymore so things like -moz-box-ordinal-group, -moz-box-orient, -moz-box-direction, -moz-box-align, -moz-box-pack or -moz-box-flex won't have any effect.

    The suggested way to deal with this is to just update your styles to use equivalent flexbox properties. Additionally, the old display: -moz-box is treated as invalid property value

    Some examples of conversions:

    • display: -moz-box -> display: flex
    • -moz-box-ordinal-group: 0 -> order: -1
    • -moz-box-orient: vertical -> flex-direction: column
    • -moz-box-direction: reverse -> flex-direction: row-reverse
    • -moz-box-align: center -> align-content: center or align-items: center depending on what you are doing.
    • -moz-box-pack: start -> justify-content: flex-start or justify-items: flex-start
    • -moz-box-flex: 10 -> flex-grow: 10

    Notes about order vs. -moz-box-ordinal-group: order supports negative values, whereas ordinal-group does not. Default value of order is 0 but default of ordinal-group is 1 so you might need to change what value to apply for it to have any effect.

    Also, see this firefox-dev post for more information.

    view more: next ›