-
Notifications
You must be signed in to change notification settings - Fork 639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-variables-1] Horizontal Review #6808
Comments
None of the items in the FAST checklist seem applicable to this specification. |
None of the items in the short I18n review checklist apply to this specification. |
2.1 What information does this feature expose, and for what purposes? |
A11y review closed with no issues |
I18N issues were submitted on 2022-03-10. |
Thanks, @aphillips I see five open issues |
Privacy review completed with no issues raised |
The security review will time-out on 8 May after three months of zero response. Previous CRD was 11 Nov 2021 Horizontal review is complete. Agenda+ to request transition to CR Snapshot. |
The CSS Working Group just discussed
The full IRC log of that discussion<dael> Topic: [css-variables-1] Horizontal Review #6808<dael> github: https://github.com//issues/6808#issuecomment-1114959228 <dael> Rossen_: Transition to CR snapshot. Understanding we're ready by end of this week <dael> Rossen_: Anything else you want to talk about before resolution <dael> chris: Not really. Went through horz review including TAG so all ready <dael> Rossen_: Awesome. Everything but security review is done; security review times out on 8 May <dael> chris: Correct <dael> Rossen_: Then in position to move to CR snapshot <dael> Rossen_: Additional comments or concerns? Otherwise will call for objections <dael> Rossen_: Obj to Move CSS Variables 1 to Snaposhot after May 9 <florian> go for it <dael> RESOLVED: Move CSS Variables 1 to Snapshot after May 9 <dael> Rossen_: chris will you handle? <dael> chris: I will <dael> Rossen_: Thanks |
Security review timed out with no response |
The text was updated successfully, but these errors were encountered: