src/popup/index.html puts text-sm (14px) on body, and Firefox draws the popup at 14px. Chrome draws it at 12px: in the pinned Playwright Chrome container the popup's body computes to font-size: 12px. Chrome adds a stylesheet of its own to extension pages, body { font-family: ...; font-size: 75% }, outside any cascade layer, and it beats Tailwind's classes, which Tailwind 4 puts in one.
This is the same cause as #418, whose fix covers the font family only. Making Chrome draw 14px would enlarge all the popup text in Chrome that takes its size from body, so whether to do it is the owner's call.
Model: opus-5-5
`src/popup/index.html` puts `text-sm` (14px) on `body`, and Firefox draws the popup at 14px. Chrome draws it at 12px: in the pinned Playwright Chrome container the popup's `body` computes to `font-size: 12px`. Chrome adds a stylesheet of its own to extension pages, `body { font-family: ...; font-size: 75% }`, outside any cascade layer, and it beats Tailwind's classes, which Tailwind 4 puts in one.
This is the same cause as https://git.eeqj.de/sneak/AutistMask/issues/418, whose fix covers the font family only. Making Chrome draw 14px would enlarge all the popup text in Chrome that takes its size from `body`, so whether to do it is the owner's call.
Model: opus-5-5
Question for the owner: should Chrome draw the popup's text at the 14px that text-sm on body declares, as Firefox already does, instead of the 12px Chrome's own extension-page stylesheet forces?
(a) Yes, match the declared 14px (recommended). The popup is designed and documented at text-sm; Firefox users already see 14px; the fix is the same one-word change #457 made for the font family, plus a check that no screen overflows the 360x600 popup in Chrome.
(b) No, keep Chrome at 12px. Nothing changes for Chrome users; the two browsers keep showing different text sizes.
Everything else continues meanwhile.
Model: opus-5-5
Question for the owner: should Chrome draw the popup's text at the 14px that `text-sm` on `body` declares, as Firefox already does, instead of the 12px Chrome's own extension-page stylesheet forces?
- **(a) Yes, match the declared 14px** (recommended). The popup is designed and documented at `text-sm`; Firefox users already see 14px; the fix is the same one-word change https://git.eeqj.de/sneak/AutistMask/pulls/457 made for the font family, plus a check that no screen overflows the 360x600 popup in Chrome.
- **(b) No, keep Chrome at 12px.** Nothing changes for Chrome users; the two browsers keep showing different text sizes.
Everything else continues meanwhile.
Model: opus-5-5
sneak
was assigned by clawbot2026-10-05 09:43:57 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
src/popup/index.htmlputstext-sm(14px) onbody, and Firefox draws the popup at 14px. Chrome draws it at 12px: in the pinned Playwright Chrome container the popup'sbodycomputes tofont-size: 12px. Chrome adds a stylesheet of its own to extension pages,body { font-family: ...; font-size: 75% }, outside any cascade layer, and it beats Tailwind's classes, which Tailwind 4 puts in one.This is the same cause as #418, whose fix covers the font family only. Making Chrome draw 14px would enlarge all the popup text in Chrome that takes its size from
body, so whether to do it is the owner's call.Model: opus-5-5
Question for the owner: should Chrome draw the popup's text at the 14px that
text-smonbodydeclares, as Firefox already does, instead of the 12px Chrome's own extension-page stylesheet forces?text-sm; Firefox users already see 14px; the fix is the same one-word change #457 made for the font family, plus a check that no screen overflows the 360x600 popup in Chrome.Everything else continues meanwhile.
Model: opus-5-5