HTML API: Consistent case sensitive handling of class names#6931
HTML API: Consistent case sensitive handling of class names#6931sirreal wants to merge 7 commits intoWordPress:trunkfrom
Conversation
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
| * 'wp-block-group' => [ WP_HTML_Tag_Processor::ADD_CLASS, 'wp-block-group'], | ||
| * 'wp-group' => [ WP_HTML_Tag_Processor::REMOVE_CLASS ], | ||
| * ); | ||
| * | ||
| * @since 6.2.0 | ||
| * @var bool[] | ||
| * @since 6.7.0 Changed the structure of values to an array | ||
| * | ||
| * @var array[] |
There was a problem hiding this comment.
We need to be able to match the class_name case insensitively, but still add whatever class was provided.
I changed the values to be an array of one of the following shapes:
[ self::ADD_CLASS, (string) $class_to_add ][ self::REMOVE_CLASS ][ self::SKIP_CLASS ]
|
This doesn't seem like the right approach, it may not align with browser behavior. |
|
#7169 is a fresh attempt at this. |
Trac ticket: https://core.trac.wordpress.org/ticket/61531
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.