Urange Parsing #15195
Merged
Urange Parsing #15195
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
Fairly exhaustively test <urange> parsing, and make sure UAs aren't cheating with specialized tokens.
Make sure that tests for should-be-valid syntax start from a stable value as well, so they don't depend on test ordering so much.
Was pretty sure selectors serialized with spaces around the combinator, but wasn't sure, and Chrome failed the test anyway. Firefox passes but with spaces, so make sure I match that.
Urange serialization isn't specified, so I shouldn't rely on the casing in this test, at least. Instead, just uppercase things, since casing doesn't matter.
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.
Fairly exhaustively test parsing, and make sure UAs aren't cheating with specialized tokens.