-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Avoid whitelist/blacklist #265
Labels
good first issue
Ideal for someone new to a WHATWG standard or software project
Comments
I'd prefer "allowed list" over "safe list". |
I prefer safelist since it can be reasonably used as a single-word term. |
I'm interested in working on this. EDIT: Nvm, vakila's got a PR on it already. |
vakila
added a commit
to vakila/html
that referenced
this issue
Oct 22, 2015
Address issue whatwg#265 (Avoid whitelist/blacklist). Replace the following word stems: * "whitelist" becomes "safelist" * "white-list" becomes "safelist" * "blacklist" becomes "blocklist" * "Blacklist" becomes "Blocklist"
bterlson
pushed a commit
to tc39/ecma262
that referenced
this issue
Mar 18, 2016
See whatwg/html#265 for context and #426 for further discussion. Closes #426.
jyasskin
added a commit
to jyasskin/fingerprinting-guidance
that referenced
this issue
Jan 9, 2020
See discussion in whatwg/html#265 and https://crbug.com/842296.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Per https://twitter.com/kthomas901/status/656157231365423104 it seems like we would do folks a favor if we avoided these terms in favor of safelist/blocklist suggested in http://english.stackexchange.com/questions/51088/alternative-term-to-blacklist-and-whitelist.
The text was updated successfully, but these errors were encountered: