Closed fantasai closed 3 years ago
This review will be discussed at our next PING meeting on 21 October 2021.
Review discussed on PING call on 21 October 2021
Go to https://github.com/w3cping/tracking-issues/issues to track the progress of any issues raised as a result of the privacy review.
Issue closed as the review has been undertaken.
(Note: there may still be outstanding privacy considerations identified in the review that have not yet been resolved.)
CSS Cascading and Inheritance Levels 4 and 5 2021-09-17 > 2021-10-31
CSS Cascading and Inheritance Levels 4 and 5
https://www.w3.org/TR/css-cascade-4/
https://www.w3.org/TR/css-cascade-5/
Note: Cascade 5 is a superset of Cascade 4, so we're sending the review requests together. See https://www.w3.org/TR/css-cascade-5/#additions-l4
Expect to transition to CR by the end of October, ideally.
Previous review request was against Level 3 (now REC)
See Privacy and Security Considerations section
Please file any issues in https://github.com/w3c/csswg-drafts/issues
Explainer for Cascade 5's new “cascade layers” feature: see minutes from Jen Simmons's presentation
Other comments:
As far as we can tell, the new features to Cascade since Level 3 do not affect privacy in any way; they just provide more sophisticated ways for authors to organize their style rules.
There is an open issue against the @import chapter to get @import fetches properly defined against the [[FETCH]] model, so that cross-origin issues, etc., are well-defined. We are attempting to fix this, but the Fetch spec is still somewhat troublesome to author against, and there are few examples of correct usage (even the HTML spec is still broken in this respect). We anticipate this will be fixed in a future CR publication, before requesting advancement to REC, and welcome any help in getting it right.
Please let us know how long to wait for your review, and let us know us if you complete review without finding any issues.