- From: jonjohnjohnson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Aug 2018 19:26:18 +0000
- To: public-css-archive@w3.org
Years ago, allowing "MQ-style invalidation" for selector lists was seen as unsafe, most likely breaking old sites and when it would "activate unexpected declaration blocks". Though I trust @dbaron's opinion on the real issues `-webkit-` prefixes have caused in gecko, are we sure making the spec tell all vendors to accept selector lists with both unsupported AND then even the supported `-webkit-` prefixed pseudos is the way forward? This will surely cause current stylesheets to behave in ways that their authors won't have realized or intended when previously seeing that those selectors "isolate" styles to webkit? > @fantasai: But this seems to be quite web-incompatible, because people depend on this behavior. > @sylvaing: How do people depend on this? > @glazou: Right now there are style rules which are fully invalid because of one selector, and authors never noticed the wasted rule. If you change, it'll start applying and change the page. > @TabAtkins: And there is some history of people using prefixed selectors in the selector list as a browser hack, and this would change the behavior they're depending on. https://www.w3.org/Style/CSS/Tracker/issues/223 http://lists.w3.org/Archives/Public/www-style/2013Apr/0246.html -- GitHub Notification of comment by jonjohnjohnson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3051#issuecomment-417075223 using your GitHub account
Received on Wednesday, 29 August 2018 19:26:19 UTC