Commits on Oct 10, 2017

1. Add size_of tests for CSS parsing error types

   

   SimonSapin committed Oct 10, 2017
   fa3ce34

2. Use arrays for error reporting test expected values

   

   SimonSapin committed Oct 10, 2017
   30e5b6f

3. Add more CSS parsing error reporting tests

   

   SimonSapin committed Oct 10, 2017
   bc0903c

4. Use the current parser location for CSS error …

   … rather than the start location of the current construct.
   This likely places the error just *after* of the unexpected token
   whereas before would be best, but that’s likely a much bigger change.
   
   See https://bugzilla.mozilla.org/show_bug.cgi?id=1378861

   

   SimonSapin committed Oct 10, 2017
   056e599

5. Update to cssparser 0.22 (source location in error types)

   

   SimonSapin committed Oct 10, 2017
   c0f8f15

6. Use the location in the error value when reporting a CSS error

   

   SimonSapin committed Oct 10, 2017
   c64374b

7. CSS parsing error types: flatten nested enums somewhat

   

   SimonSapin committed Oct 10, 2017
   46ea99d

8. CSS parsing error types: flatten nested enums some more

   

   SimonSapin committed Oct 10, 2017
   1a04108

9. CSS parsing error types: flatten nested enums more still

   

   SimonSapin committed Oct 10, 2017

   Loading status checks…
   c36ac69