Changeset 48121 for trunk/src/wp-includes/theme.php

Timestamp:

06/22/2020 05:24:34 PM (4 years ago)

Author:

desrosj

Message:

General: Remove “whitelist” and “blacklist” in favor of more clear and inclusive language.

“The WordPress open source community cares about diversity. We strive to maintain a welcoming environment where everyone can feel included.”

With this commit, all occurrences of “whitelist” and “blacklist” (with the single exception of the $new_whitelist_options global variable) are removed. A new ticket has been opened to explore renaming the $new_whitelist_options variable (#50434).

Changing to more specific names or rewording sentences containing these terms not only makes the code more inclusive, but also helps provide clarity. These terms are often ambiguous. What is being blocked or allowed is not always immediately clear. This can make it more difficult for non-native English speakers to read through the codebase.

Words matter. If one contributor feels more welcome because these terms are removed, this was worth the effort.

Props strangerstudios, jorbin, desrosj, joemcgill, timothyblynjacobs, ocean90, ayeshrajans, davidbaumwald, earnjam.
See #48900, #50434.
Fixes #50413.

File:

• trunk/src/wp-includes/theme.php (modified) (2 diffs)

trunk/src/wp-includes/theme.php

@@ -2824 +2824 @@
  */
 function remove_theme_support( $feature ) {
-    // Blacklist: for internal registrations not used directly by themes.
+    // Do not remove internal registrations that are not used directly by themes.
     if ( in_array( $feature, array( 'editor-style', 'widgets', 'menus' ), true ) ) {
         return false;
@@ -2833 +2833 @@
 
 /**
- * Do not use. Removes theme support internally, ignorant of the blacklist.
+ * Do not use. Removes theme support internally without knowledge of those not used by
+ * themes directly.
  *
  * @access private
  * @since 3.1.0
- *
  * @global array               $_wp_theme_features
  * @global Custom_Image_Header $custom_image_header