- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Apr 2020 00:25:57 +0000
- To: public-css-archive@w3.org
mirisuzanne has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-cascade] What is the migration path for custom origins? == This is in relation to #4470 custom-origin proposal. To quote @frivoal in the transcript from our original discussion: > florian: One thing I'm a little concerned is how we figure out the syntax to have a migration path toward this from legacy CSS. > florian: In particular, a syntax ignorable by old browsers is bad because the cascade will be all mushed up; but making it hide rules from old browsers means they'll just miss a lot of code. > florian: Writing everything twice is bad, but not having an upgrade path is bad. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4985 using your GitHub account
Received on Wednesday, 22 April 2020 00:25:59 UTC