The company has already started this work, but given the protests and the situation, Chrome developers want to change all possibly user-facing instances of “Blacklist” and “Whitelist” in Chrome.
As is well known, the world is not only going through the Covid-19 pandemic but also fighting racist ideas in every possible way through the “Black Lives Matter” protests. Google has offered support for this but hasn’t done more. Last October, the search giant included guidance in its official code style guide on how to write “racially neutral” code. As part of that document, it also includes that terms like “Blacklist” and “Whitelist” should be avoided in coding and replaced with terms like “Blocklist” and “Allowlist.”
According to 9to5Google, the company has already started this work, but given the protests and the situation, Chrome developers want to change all possibly user-facing instances of “Blacklist” and “Whitelist.” Although these will still exist on the backend.
The news comes from a new code change submitted on Chromium, attempting to remove “Blacklist” and “Whitelist” from all places visible to the end user. “This is the first of two changes renaming components/blacklist to components/blocklist. This includes all class/method/member/variable renames. There should be no functional difference here. This patch will be followed by another patch that renames directories/files and updates the necessary build system rules. The vast majority of the changes are simply replacing the ‘a’ with an ‘o’.”
Currently, it’s said about 2,000 references to “Blacklist” have been replaced. It’s unclear when this will be finished or whether the company has already started it. But it’s good to see people in different industries opposing racism in their own fields.