-
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: Fix unsupported insertion mode messages #7043
HTML API: Fix unsupported insertion mode messages #7043
Conversation
Insertion modes may include instructions like "process the token in another insertion mode." This means that the step_in_X method may be called to process in the insertion mode _without_ changing the state of the insertion mode. This can result in unsupported errors that are incorrect. The bail messages for each step_in_ method should explicitly mention its insertion mode to ensure the error messages are correct.
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. |
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.
Great catch, thanks @sirreal
Insertion modes in an HTML parser may include instructions like "process the token in the IN HEAD insertion mode." The rules do not change the insertion mode of the parser, but the errors are triggered outside of the rules for the current insertion mode. These will be misleading when bailing on these instructions, because it will point someone to the wrong place in the code to find the source of the error. In this patch all of the bail-points due to lacking insertion mode support are hard-coded to better orient someone to the section of the code lacking support for handling the input HTML. Developed in #7043 Discussed in https://core.trac.wordpress.org/ticket/61576 Follow-up to [58679]. Props: dmsnell, jonsurrell. See #61576. git-svn-id: https://develop.svn.wordpress.org/trunk@58781 602fd350-edb4-49c9-b593-d223f7449a82
Insertion modes in an HTML parser may include instructions like "process the token in the IN HEAD insertion mode." The rules do not change the insertion mode of the parser, but the errors are triggered outside of the rules for the current insertion mode. These will be misleading when bailing on these instructions, because it will point someone to the wrong place in the code to find the source of the error. In this patch all of the bail-points due to lacking insertion mode support are hard-coded to better orient someone to the section of the code lacking support for handling the input HTML. Developed in WordPress/wordpress-develop#7043 Discussed in https://core.trac.wordpress.org/ticket/61576 Follow-up to [58679]. Props: dmsnell, jonsurrell. See #61576. Built from https://develop.svn.wordpress.org/trunk@58781 git-svn-id: http://core.svn.wordpress.org/trunk@58183 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Insertion modes in an HTML parser may include instructions like "process the token in the IN HEAD insertion mode." The rules do not change the insertion mode of the parser, but the errors are triggered outside of the rules for the current insertion mode. These will be misleading when bailing on these instructions, because it will point someone to the wrong place in the code to find the source of the error. In this patch all of the bail-points due to lacking insertion mode support are hard-coded to better orient someone to the section of the code lacking support for handling the input HTML. Developed in WordPress/wordpress-develop#7043 Discussed in https://core.trac.wordpress.org/ticket/61576 Follow-up to [58679]. Props: dmsnell, jonsurrell. See #61576. Built from https://develop.svn.wordpress.org/trunk@58781 git-svn-id: https://core.svn.wordpress.org/trunk@58183 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Insertion modes in an HTML parser may include instructions like "process the token in the IN HEAD insertion mode." The rules do not change the insertion mode of the parser, but the errors are triggered outside of the rules for the current insertion mode. These will be misleading when bailing on these instructions, because it will point someone to the wrong place in the code to find the source of the error. In this patch all of the bail-points due to lacking insertion mode support are hard-coded to better orient someone to the section of the code lacking support for handling the input HTML. Developed in WordPress#7043 Discussed in https://core.trac.wordpress.org/ticket/61576 Follow-up to [58679]. Props: dmsnell, jonsurrell. See #61576. git-svn-id: https://develop.svn.wordpress.org/trunk@58781 602fd350-edb4-49c9-b593-d223f7449a82
Insertion modes may include instructions like "process the token in
another insertion mode." This means that the step_in_X method may be
called to process in the insertion mode without changing the
state of the insertion mode.
This can result in unsupported errors that are incorrect.
The bail messages for each step_in_ method should explicitly
mention its insertion mode to ensure the error messages are
correct.
Trac ticket: https://core.trac.wordpress.org/ticket/61576
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.