-
Notifications
You must be signed in to change notification settings - Fork 715
[css-module-bikeshed] Add 'Privacy and Security Considerations' section #240
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
Comments
After discussiong PR #241 with @frivoal it came to my mind that maybe the editors wait until their spec. stabalized, i.e. is in CR or PR, to add that section and use the Bikeshed warning as note that they still need to add it. Is that assumption correct? If not, should an issue be added to the spec. for this as suggested by Florian? Sebastian |
No, there's no actual reasoning behind leaving it out, besides that it's additional effort and usually low-value for CSS specs. Marking the contents as an issue is fine. |
Ok, I've done that in #241. Sebastian |
danke! |
Bitte! 😄 |
Uh oh!
There was an error while loading. Please reload this page.
To pass the Bikeshed parsing without warnings there should be a Privacy and Security Considerations section added.
This also pushes editors to add that information to their specs.
Sebastian
The text was updated successfully, but these errors were encountered: