Make WordPress Core

04/19/2023 09:25:32 AM (14 months ago)
Bernhard Reiter

HTML API: Ensure attribute updates happen only once for case variants.

When setting a new value for an attribute multiple times and providing
multiple case variations of the attribute name the Tag Processor has
been appending multiple copies of the attribute into the updated HTML.

This means that only the first attribute set determines the value in
the final output, plus the output will appear wrong.

In this patch we're adding a test to catch the situation and resolving it
by using the appropriate comparable attribute name as a key for storing
the updates as we go. Previously we stored updates to the attribute by
its given $name, but when a new update of the same name with a
case variant was queued, it would not override the previously-enqueued
value as it out to have.

Props dmsnell, zieladam.
Fixes #58146.

1 edited


  • trunk/src/wp-includes/html-api/class-wp-html-tag-processor.php

    r55619 r55659  
    18161816     *
    18171817     * @since 6.2.0
     1818     * @since 6.2.1 Fix: Only create a single update for multiple calls with case-variant attribute names.
    18181819     *
    18191820     * @param string      $name  The attribute name to target.
    19081909             *    Result: <div id="new"/>
    19091910             */
    1910             $existing_attribute             = $this->attributes[ $comparable_name ];
    1911             $this->lexical_updates[ $name ] = new WP_HTML_Text_Replacement(
     1911            $existing_attribute = $this->attributes[ $comparable_name ];
     1912            $this->lexical_updates[ $comparable_name ] = new WP_HTML_Text_Replacement(
    19121913                $existing_attribute->start,
    19131914                $existing_attribute->end,
Note: See TracChangeset for help on using the changeset viewer.