So it turns out our locally-scoped CSS reset actually solved an issue. One of our legacy apps ended up with two copies of our design system (long story) and we were able to avoid specificity issues by ensuring that each reset only targeted the components for that version.
-
-
A dynamic locally-scoped reset is something I've been trying to implement for a long time. How did you handle the CSS duplication of common resets, or is it trivial? Please could you share the example? Would love to see more of this than the usual hamfisted global resets
-
This is our reset: https://github.com/seek-oss/braid-design-system/blob/master/lib/reset/reset.treat.ts … Note how we set up all the individual reusable reset classes, then export an object that maps tag names to classes. (Yes, this is TypeScript, but we execute this at build time and generate static CSS)
- Još 1 odgovor
Novi razgovor -
-
-
CODE RED
THIS IS NOT A MEMEHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
CSS Modules co-creator,
OSS / UI / design / tooling at 

