- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 Jan 2024 19:01:28 +0000
- To: public-css-archive@w3.org
> I also find it confusing to think about which features go into which level. FWIW, this hasn't been a concern for me. We are working on new features, on regular intervals we decide which features need to stabilize that go into the next level. The decision for which level something is deferred to is on a case by case basis. For example, the spec for same-document transitions (and other features in L1) was fairly stable so decided to cut off there and defer cross-document transitions to L2. It's the fact that patching algorithms in lower levels for features in higher levels becomes very messy. If the solution is to re-define algorithms, I can live with that. Whenever we do this, we can leave a non-normative note indicating the highest level which replaces an algorithm. We are gearing up towards a FPWD of L2 since cross-document transitions is pretty close so would love to get this resolved soon. -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9850#issuecomment-1910809560 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 January 2024 19:01:31 UTC