-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTML API: Join successive text nodes in html5lib test representation. #6984
HTML API: Join successive text nodes in html5lib test representation. #6984
Conversation
Many tests from the html5lib test suite fail because of differences in text handling between a DOM API and the HTML API, even though the semantics of the parse are equivalent. For example, it's possible in the HTML API to read multiple successive text nodes when the tokens between them are ignored. The test suite didn't account for this and so was failing tests. This patch improves the construction of the representation to compare against the test suite so that those tests don't fail inaccurately.
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. |
Trac Ticket MissingThis pull request is missing a link to a Trac ticket. For a contribution to be considered, there must be a corresponding ticket in Trac. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. More information about contributing to WordPress on GitHub can be found in the Core Handbook. |
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense 👍
Many tests from the html5lib test suite fail because of differences in text handling between a DOM API and the HTML API, even though the semantics of the parse are equivalent. For example, it's possible in the HTML API to read multiple successive text nodes when the tokens between them are ignored. The test suite didn't account for this and so was failing tests. This patch improves the construction of the representation to compare against the test suite so that those tests don't fail inaccurately. Developed in #6984 Discussed in https://core.trac.wordpress.org/ticket/61576 Props bernhard-reiter, dmsnell, jonsurrell. See #61576. git-svn-id: https://develop.svn.wordpress.org/trunk@58712 602fd350-edb4-49c9-b593-d223f7449a82
Many tests from the html5lib test suite fail because of differences in text handling between a DOM API and the HTML API, even though the semantics of the parse are equivalent. For example, it's possible in the HTML API to read multiple successive text nodes when the tokens between them are ignored. The test suite didn't account for this and so was failing tests. This patch improves the construction of the representation to compare against the test suite so that those tests don't fail inaccurately. Developed in WordPress/wordpress-develop#6984 Discussed in https://core.trac.wordpress.org/ticket/61576 Props bernhard-reiter, dmsnell, jonsurrell. See #61576. Built from https://develop.svn.wordpress.org/trunk@58712 git-svn-id: http://core.svn.wordpress.org/trunk@58114 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Many tests from the html5lib test suite fail because of differences in text handling between a DOM API and the HTML API, even though the semantics of the parse are equivalent. For example, it's possible in the HTML API to read multiple successive text nodes when the tokens between them are ignored. The test suite didn't account for this and so was failing tests. This patch improves the construction of the representation to compare against the test suite so that those tests don't fail inaccurately. Developed in WordPress/wordpress-develop#6984 Discussed in https://core.trac.wordpress.org/ticket/61576 Props bernhard-reiter, dmsnell, jonsurrell. See #61576. Built from https://develop.svn.wordpress.org/trunk@58712 git-svn-id: https://core.svn.wordpress.org/trunk@58114 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Many tests from the html5lib test suite fail because of differences in text handling between a DOM API and the HTML API, even though the semantics of the parse are equivalent. For example, it's possible in the HTML API to read multiple successive text nodes when the tokens between them are ignored. The test suite didn't account for this and so was failing tests. This patch improves the construction of the representation to compare against the test suite so that those tests don't fail inaccurately. Developed in WordPress#6984 Discussed in https://core.trac.wordpress.org/ticket/61576 Props bernhard-reiter, dmsnell, jonsurrell. See #61576. git-svn-id: https://develop.svn.wordpress.org/trunk@58712 602fd350-edb4-49c9-b593-d223f7449a82
Trac ticket: Core-61576
Many tests from the html5lib test suite fail because of differences in
text handling between a DOM API and the HTML API, even though the
semantics of the parse are equivalent. For example, it's possible in
the HTML API to read multiple successive text nodes when the tokens
between them are ignored.
The test suite didn't account for this and so was failing tests. This
patch improves the construction of the representation to compare
against the test suite so that those tests don't fail inaccurately.
Testing
Several tests were able to be removed from the skip group after this change.