The floating header's backdrop blur makes the pill a containing block
for fixed-position descendants, so the fullscreen mobile menu rendered
at the pill's height instead of filling the viewport. Lift the filter
while the menu is open. Fixes#3057.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The submenu panel carried both `pt-2` and `p-5`. Tailwind emits shorthand
utilities before their longhand counterparts, so `padding-top` resolved to
`0.5rem` while the other three sides stayed at `1.25rem`, regardless of the
order the classes appear in the markup. The first submenu entry sat flush
against the top edge.
This went unnoticed while the panel was translucent. v3 made it opaque, which
draws the edge and exposes the imbalance.
Drop `pt-2` so the panel keeps the uniform `p-5` it was styled for. No new
utility classes, so the compiled stylesheet is unchanged.
Darken burufugu primary-600 to pass 4.5:1 on white, bump the search
shortcut hint to neutral-500, and surface the language switcher in
the visible mobile header row instead of the menu dialog.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The fixed wrappers relied on their static position resolving to y=0 as
direct flex children of body; the header landmark added in #3048 made
that position fall below the spacer. Set top-0 on all fixed variants.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Wrap the page header in a header element and the subnavigation menu in
a labelled nav landmark. Addresses #3023.
Co-authored-by: Chris Herborth <chrish@taffer.ca>
Dynamically update the appearance switcher accessibility labels and tooltips using the native i18n variables so that the UI correctly reflects the user's localized language instead of hardcoded English strings.
- Add "default" option to font size selector to respect user's original CSS
- Clear localStorage font setting when "default" is selected
- This prevent overriding user's custom font-size declarations on first load
This fixes the following issue in Chrome: No label associated with a form field.
I don't know why a <label> was used here before, but I see no reason to do so, a div works just as well.
ZhenShuo Leo