- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 03 Feb 2022 22:58:17 +0000
- To: public-css-archive@w3.org
Right, @FremyCompany's point is that this wouldn't, in any meaningful sense, "just work". You're still missing all your layered styles. It seems like you're operating on the theory that this is similar to JS and "progressive enhancement", where you can design a basic experience using older tech (like writing an app using `<a>`s and several distinct pages) and then layer new fancy tech on top for a better experience in new browsers (like using `fetch()` to turn it into a single-page app). That's not the case here; layers aren't cool new tech, they're organizational. The stuff you put in layers is identical to the stuff not in layers; there's no dividing line to draw in terms of "enhancement". This is much more similar to switching to JS arrow functions over the old `function` declarations; the code is identical in behavior either way, it's just more convenient to write with the new stuff. You wouldn't separate out your code into "basic" stuff using `function` and "new, better" stuff using arrow funcs that's okay to be skipped in older browsers. You'd either use `function` everywhere, or use arrow funcs and a JS compiler to turn it into old-browser-compatible code, or just wait until arrow funcs are widely supported and ignore the minority of older browsers. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-1029478610 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 3 February 2022 22:58:19 UTC