[:is/:where] Test selector serialization rather than parse status
We currently have several unit tests that check that some selector list containing :is or :where either fails or passes parsing. That's all well and good when selector lists are parsed the normal way, but with <forgiving-selector-list> [1] support (in a future CL), a simple selector :is(...) can't really fail parsing: it will just end up empty in the worst case. Hence, this CL makes preparations such that it's easier to write tests for these "partial" parse failures. While at it, tests are also converted to parametric tests. This makes it easier to run individual tests when something is failing. There should be no behavior change, nor any change in test coverage. [1] https://drafts.csswg.org/selectors/#typedef-forgiving-selector-list Bug: 568705 Change-Id: I81119599d378a5067cd3d08c5dbdc7e3de2f1ae2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2450153Reviewed-by:Rune Lillesveen <futhark@chromium.org> Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org> Cr-Commit-Position: refs/heads/master@{#814120}
Showing
Please register or sign in to comment