[–] 1 point 1 month ago

That extra spacer/drag space for Vertical tabs mode only appeared in Firefox's UI a couple of updates ago.

Likewise the extra flexible spaces either side of the 'List all tabs' button... easy to miss if not creating a new profile.

  • source
  • parent
  • context
  • [–] [S] 1 point 2 months ago* (last edited 2 months ago)

    Thank you very much for the reply and pointer to your own updated scrollbars style 'scrollable_menupopups.css'... which I had somehow managed to miss for at least the last 3 years... all whilst recommending your excellent repo's contents to others on numerous occasions!

    More information on the recent changes to scrollbar styling in GitHub repo Issue #654 'scrollable_menupopups.css in V154 V155'.

    Likely a facet of human nature not to look for alternative solutions to a problem that has already been solved.

  • source
  •  

    This extremely useful style which added scrollbars to all long Bookmarks folders was broken by the Fx155.0 update... unsure why?

    The style was originally posted by OP nollinvoyd in his March 2023 r/FirefoxCSS topic 'Scrollbars for all bookmarks folders' and had worked flawlessly since up to and including the Fx154 stable release.

    /*** Scrollbar for long Bookmark menu "popups" ***/
    
    [placespopup="true"] { --allow-scroll-bar: auto; }
    
    scrollbox[part="scrollbox"] { overflow-y: var(--allow-scroll-bar, inherit) !important; }
    

    Unsure what has changed in Fx155... possibly the variable --allow-scroll-bar has been changed or removed? Unable to find any related bug after searching the huge 'Target Milestone 155' Bug list.

     

    Many previous Findbar userstyles broken by the Fx155.0 update including 'floating_findbar_on_top.css'... which now appears as a thin squashed line at the bottom of the Content window/Viewport.

    Other Findbar styles reported similar problems in r/FirefoxCSS topic 'Firefox version 155 broke an old userchrome.css I was using to change the findbar.'

    [–] 1 point 2 months ago* (last edited 2 months ago) (1 child)

    Using a capital 'C' in 'userChrome.css' and userContent.css file names is a longstanding convention... but not a requirement.

    Edit: CSS userChrome modifications work normally in Firefox on Windows OS' with a small 'c' in the 'userchrome.css' file name... unable to test if this also applies for macOS and Linux installations.

  • source
  • parent
  • context