Skip to content

Fix case-insensitive dimension/keyword determination #71

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

Closed
wants to merge 1 commit into from
Closed

Fix case-insensitive dimension/keyword determination #71

wants to merge 1 commit into from

Conversation

slusarz
Copy link
Contributor

@slusarz slusarz commented Oct 23, 2013

The test-case was a bit broken though - it changed the case of the Hz
keyword which isn't clear from the documentation. Better solution is to
preserve the case in the original input.

The test-case was a bit broken though - it changed the case of the Hz
keyword which isn't clear from the documentation.  Better solution is to
preserve the case in the original input.
@sabberworm
Copy link
Collaborator

No, the test case was not broken. The CSS parser is designed to parse valid CSS but to parse it into comparable structures which it won’t be if we leave the case intact for case-insensitive tokens.. Besides, I wasn’t telling you so you could fix this, I already have a fix.

@sabberworm sabberworm closed this Oct 23, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants