src/popup/index.html puts font-mono on the body element, and Firefox draws the popup in that monospace font. Chromium does not: in the pinned Playwright container the popup's text computes to "WenQuanYi Zen Hei", Arial, sans-serif, the container's system font, while the Firefox container computes the declared ui-monospace, ... monospace stack.
Likely cause, not verified: Chrome adds its own stylesheet to extension pages that sets the font on body, and Tailwind 4 puts its utilities in a CSS cascade layer, which any rule outside a layer beats whatever its specificity, so font-mono loses.
Effects: the popup looks different in the two browsers, and anything sized for monospace text, such as the one-line flash messages from #252, is only exercised as users see it in Firefox; the Chrome end-to-end suite renders the narrower system font.
Model: opus-5-5
`src/popup/index.html` puts `font-mono` on the `body` element, and Firefox draws the popup in that monospace font. Chromium does not: in the pinned Playwright container the popup's text computes to `"WenQuanYi Zen Hei", Arial, sans-serif`, the container's system font, while the Firefox container computes the declared `ui-monospace, ... monospace` stack.
Likely cause, not verified: Chrome adds its own stylesheet to extension pages that sets the font on `body`, and Tailwind 4 puts its utilities in a CSS cascade layer, which any rule outside a layer beats whatever its specificity, so `font-mono` loses.
Effects: the popup looks different in the two browsers, and anything sized for monospace text, such as the one-line flash messages from https://git.eeqj.de/sneak/AutistMask/issues/252, is only exercised as users see it in Firefox; the Chrome end-to-end suite renders the narrower system font.
Model: opus-5-5
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.htmlputsfont-monoon thebodyelement, and Firefox draws the popup in that monospace font. Chromium does not: in the pinned Playwright container the popup's text computes to"WenQuanYi Zen Hei", Arial, sans-serif, the container's system font, while the Firefox container computes the declaredui-monospace, ... monospacestack.Likely cause, not verified: Chrome adds its own stylesheet to extension pages that sets the font on
body, and Tailwind 4 puts its utilities in a CSS cascade layer, which any rule outside a layer beats whatever its specificity, sofont-monoloses.Effects: the popup looks different in the two browsers, and anything sized for monospace text, such as the one-line flash messages from #252, is only exercised as users see it in Firefox; the Chrome end-to-end suite renders the narrower system font.
Model: opus-5-5