This makes tabs scrollboxes have display:contents and thus makes tabs
use tabbrowser-tabs as their parent container.
Reason being that in firefox 141 the pinned tabs are moved to separate
scrollbox which would then have it's own display block.
Fixes#551
We already apply computed top margin to notification popup and
permission popup so that they are visible. But it seems that if the
panel is close enough to screen bottom edge (such as in maximized
windows) then the panel contents fail typically fail to render. For
whatever reason, changing the default margin for
customizationui-widget-panel makes the failures much less frequent
although it doesn't appear to get rid of the issue completely.
When the user exits customize mode, Firefox re-evaluates urlbar
dimensions and the result ends up with --urlbar-height becoming 0px
since the urlbar gets hidden.
The input box uses --urlbar-height to calculate its block padding which
in turn evaluates to full urlbar-height - thus making the contents of
input-box 0px leading to "invisible" input-box.
As a workaround we now clamp the padding-block calculation to 4px.
If bookmarks toolbar is empty (except for the flex space) the
empty-toolbar indicator element is visible, which causes the flex-space
to be be center-aligned - this is simply fixed with order: -1
In addition, when letterboxing is enabled and window is somewhat narrow,
the Done ::before pseudo can cause the statuspanel to be wider that the
<browser> element, which causes the <browser> to move when links are
being hovered. So lets just make the Done label absolute.
We have removed custom browser top margin in fullscreen mode, but it
actually needs to apply in fullscreen mode if toolbars are not
autohidden using built-in Firefox fullscreen mechanism.
Transforming the <image> element causes it to become smaller, and thus
to not trigger click event if the button was clicked near the edge.
This patch makes us scale tab close button by instead changing its
padding which just makes the icon smaller during :active.
This fixes#526
Bookmarks toolbar doesn't have --toolbar-bgcolor when vertical tabs is
enabled.
We need to inherit background-color from toolbox though, because
otherwise the toolbar would be transparent if the selected theme doesn't
have image backgrounds.
On Windows 10 at least, the -1px static bottom margin we were using
causes a empty row of pixels to appear between tabs toolbar and nav-bar
when: 1. compact mode is used and 2. window scaling is at least 120% and
3. menubar is disabled.
This might be useful to be made to apply to Windows only, but that needs
testing. I suspect that this is also somewhat system dependent or
depends on more than just display scaling and density.
Since Tabs toolbar and menubar are direct children of toolbox
.browser-toolbar selector would apply to them as well causing certain
rendering issues such as slight movements in buttons when toolbox is
hovered
Firefox 135 uses resize observer to toggle the expanded state, so the
attribute will get removed when autohide makes the tabs collapse. Thus,
we cannot differentiate between manually collapsed and expanded states.
Note, this only affects Firefox 136+ with its new audio button.
This patch also restricts the style to horizontal tabs because Vertical
tabs can be collapsed with built-in feature.
At least on linux permissions-popup and notification-popup panels
don't get side=bottom attribute so the open downwards which causes them to
be drawn outside of screen. Fixes#493
Because the toolbox has display: contents, we need to display the background
separately for each toolbars. In addtion, on linux the main-window has
transparent background-color so we need to set toolbar opacity to 1 to
prevent transparent window areas.
This makes the line not reserve any space which is great for tab-groups
support. This patch also adds some new selectors for other tab-group
related things.
Fixes#494
The old selector expected .tabbrowser-tab to be a child of the
arrowscrollbox, which isn't necessarily the case anymore with groups.
This patch also removes a few very old rules not that are not used
anymore.
This means that the button will be hidden in ESR 128, but on Firefox
132+ it won't be since one can simply remove the button themselves or
move it to another toolbar etc. Fixes#407
