Fixed issue parsing elements with mixed valid and invalid mf2 classnames #231
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…mes on Previously, an element with an invalid root classname such as would correctly not get parsed into a -type mf struct, but the h-12 would prevent the element from being parsed for valid classnames. This is now fixed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, an element with an invalid root classname such as
h-12wouldcorrectly not get parsed into a
h-12-type mf struct, but the h-12 wouldprevent the element from being parsed for valid classnames. This is now fixed.
In the process, I improved some inconsistent logic for determining whether an element has root MF classes, and enabled PHP functions to be registered on the parser DOMXPath object.
Fixes #230