Skip to content

unicode-range is incorrectly rejected in some cases #133

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
upsuper opened this issue Apr 11, 2017 · 0 comments
Closed

unicode-range is incorrectly rejected in some cases #133

upsuper opened this issue Apr 11, 2017 · 0 comments

Comments

@upsuper
Copy link
Contributor

upsuper commented Apr 11, 2017

A minimal reproducible example is:

<!DOCTYPE HTML>
<style>
  @font-face { unicode-range: U+2 , U+???; }
</style>
<script>
  alert(document.styleSheets[0].cssRules[0].style.getPropertyValue('unicode-range'));
</script>
SimonSapin added a commit that referenced this issue Apr 11, 2017
Unexpected tokens after U+<integer> are not an error,
just not part of the <unicode-range>.
bors-servo pushed a commit that referenced this issue Apr 11, 2017
Fix #133 <unicode-range> parsing corner case

Unexpected tokens after U+<integer> are not an error, just not part of the <unicode-range>.

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/rust-cssparser/134)
<!-- Reviewable:end -->
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

No branches or pull requests

1 participant