ISSUE-223: Should Selectors adopt MQ-style invalidation (per comma-separated group)?
Should Selectors adopt MQ-style invalidation (per comma-separated group)?
- State:
- CLOSED
- Product:
- Selectors Level 4
- Raised by:
- Florian Rivoal
- Opened on:
- 2012-02-09
- Description:
- No Change.
- Related Actions Items:
- No related actions
- Related emails:
- Re: [selectors4] Open issues (from fantasai.lists@inkedblade.net on 2013-04-17)
- [selectors4] Open issues (from fantasai.lists@inkedblade.net on 2013-04-08)
- Re: Allowing unknown pseudo classes and unknown pseudo element in the selector. (from florianr@opera.com on 2012-03-09)
- CSS-ISSUE-223: Should Selectors adopt MQ-style invalidation (per comma-separated group)? [Selectors Level 4] (from sysbot+tracker@w3.org on 2012-02-09)
Related notes:
Is the rationale for this issue described somewhere?
David Baron, 9 Feb 2012, 18:06:50Not described anywhere so far, but here is the idea: As we work on new levels of selectors, new possibilities are being introduced, and of course, they will not be simultaneously supported in all browsers. This means combining newish selectors with old ones using commas isn't safe, as old browsers would discard everything, not just the bit they don't understand. This encourages authors to duplicate declaration blocks instead of using comma separated selectors. Invalidating per comma separated group, rather than the entire selector, like media queries do, would fix this.
That said, glazou has already mostly talked me out of this, on the argument that this would break the web. Previously failing selectors may start to match, and activate unexpected declaration blocks.
If we can do this without breaking the web, I think it would be nice, but as this is not critical, maybe it isn't worth the risk.
Display change log
