Emilio Cobos Álvarez
Emilio Cobos Álvarez
For the `white-space: pre` issue that can probably be removed? Gecko at least doesn't have it unless I'm missing something.
Ah, I guess gecko has `white-space: nowrap !important`. But we could make that part of the internal box styles for the `none` / `auto` case.
@nt1m you mean `select::decoration` (or something)? And how so? You can use styles for the internal anonymous box when appearance isn't `base`, and make `base` give you a regular box.
What kinds of differences do we want between `none` and `base`? Most controls with `none` look reasonable (checkbox / radio being the exception). My preference would be to keep the...
@annevk not necessarily. The box tree might change without the shadow tree having to change. E.g. the shadow tree could be the same, but `appearance: auto` might create a replaced...
`appearance: none` has some compat requirements for e.g., `` that might prevent it from just creating boxes for its children regularly. I'd expect `appearance: none` for select to keep creating...
Not saying it's necessarily a good idea, but playing devil's advocate a bit, we already have that kind of concept for e.g. `@import` / `@namespace` / etc, don't we? Imagine...
An argument for keeping it could be performance, mostly. E.g., if you do something like: ```css .foo { --bar: baz; @media (a) { --bar: something-else; } --baz: ...; @media (b)...
There's the cargo expand feature that should work, right?
can we get this merged? Would be good to avoid unnecessary duplicate dependencies