Skip to content

CSS regression on staging #10908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
LawnGnome opened this issue Mar 27, 2025 · 1 comment · Fixed by #10912
Closed

CSS regression on staging #10908

LawnGnome opened this issue Mar 27, 2025 · 1 comment · Fixed by #10912
Labels
A-frontend 🐹 B-needs-investigation C-bug 🐞 Category: unintended, undesired behavior

Comments

@LawnGnome
Copy link
Contributor

For more context, see this thread on Zulip.

Right now on staging (v5005, commit 417f446), there's obvious CSS breakage: links are the wrong colours, the social icons are massive, and various other things just look off. Here's a screenshot:

Image

Using git bisect and building the frontend with pnpm run build hints that the issue began with 139824d, but I'm somewhat dubious about this in practice, since that was in December.

Looking at the CSS being served on staging versus production, it's pretty obvious that there are just a whole bunch of rules and selectors not being included. I haven't had a chance to analyse specifically where the missing rules are coming from to see if there are one or more CSS modules that are obviously missing.

@LawnGnome LawnGnome added A-frontend 🐹 B-needs-investigation C-bug 🐞 Category: unintended, undesired behavior labels Mar 27, 2025
@eth3lbert
Copy link
Contributor

It looks like the nesting rules are all gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend 🐹 B-needs-investigation C-bug 🐞 Category: unintended, undesired behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants