- From: j. redhead via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Feb 2023 22:46:16 +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. ***If*** unlayered rules came first instead of last, then I don't see why you couldn't just use old-fashioned methods to construct a basic reset+layout style that is just barely good enough, then (lazily :P) use the new hotness (layers) to do themes & everything else. Sure, it would be *highly* unorthodox. But well within the realms of possibility (unless I am missing something). Just as you *could* choose to define some fundamental/barebones functions in one JS file, then in another file using newer syntax, override those barebone functions and/or define "extra" functions that are only called if defined. Granted, I can't think of a single reason why you'd *ever* want to do this with JS. But the CSS example is salient & tempting. -- GitHub Notification of comment by jeremyredhead Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6323#issuecomment-1419887700 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 6 February 2023 22:46:17 UTC