Skip to content

Commit

Permalink
Documentation: isEquivalentHTML: Fix incorrect spec
Browse files Browse the repository at this point in the history
As of #22506 (May 2020), `isEquivalentHTML` short-circuits if its two
given strings are identical, and thus no longer treats invalid HTML
differently. Remove the mention of special handling, which had been
introduced in #8304 (August 2018).
  • Loading branch information
mcsf committed Aug 5, 2021
1 parent d60698a commit fd5d476
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions packages/blocks/src/api/validation/index.js
Original file line number Diff line number Diff line change
Expand Up @@ -590,8 +590,7 @@ export function isClosedByToken( currentToken, nextToken ) {

/**
* Returns true if the given HTML strings are effectively equivalent, or
* false otherwise. Invalid HTML is not considered equivalent, even if the
* strings directly match.
* false otherwise.
*
* @param {string} actual Actual HTML string.
* @param {string} expected Expected HTML string.
Expand Down

0 comments on commit fd5d476

Please sign in to comment.