Skip to content

Added 'Privacy and Security Considerations' section to CSS Bikeshed Module #241

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.

Sign up for GitHub

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

Merged
tabatkins merged 2 commits into from
Jun 27, 2016
Merged

Added 'Privacy and Security Considerations' section to CSS Bikeshed Module #241

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b671f42
[css-module-bikeshed] Added 'Privacy and Security Considerations'
SebastianZ Jun 25, 2016
3ab3e2b
Turned contents of 'Privacy and Security Considerations' section into
SebastianZ Jun 27, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
[css-module-bikeshed] Added 'Privacy and Security Considerations' 
section
  • Loading branch information
@SebastianZ
SebastianZ committed Jun 25, 2016
commit b671f428f30663cc026dfd5ba767f05a91e9fbb1
4 changes: 4 additions & 0 deletions css-module-bikeshed/Overview.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -159,3 +159,7 @@ Internal display model: the 'foo' property {#the-foo-property}
DOMString baz = "qux";
};
</pre>

<h2 class=no-num id=priv-sec>Privacy and Security Considerations</h2>

Make some considerations about privacy and security.
Copy link
Collaborator

@frivoal frivoal Jun 26, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about making this “Make some considerations about privacy and security.” into an issue, to make sure it doesn't get forgotten?

Copy link
Contributor Author

@SebastianZ SebastianZ Jun 26, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have a strong opinion about that, but there is no other issue marking a 'must edit'.

Sebastian

Copy link
Collaborator

@frivoal frivoal Jun 27, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well, adding this to the template only serves to silence a Bikeshed warning telling you you need to write this part. If we replace the warning with an issue in the spec, that's fine, but there was a reason for that warning: this is a part of the spec that is at risk of being forgotten unless you are explicitly reminded about.

Copy link
Contributor Author

@SebastianZ SebastianZ Jun 27, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That it can be easily forgotten is one reason I opened issue #240.
Obviously very few editors actually added this section to their specs so far. So it seemed to me the Bikeshed warning is not enough and I was wondering about how to push people more to add that section.

It's ok for me to add an issue instead, though before I do that I'm asking about this at #240 (comment).

Sebastian