tree 8d2669e0edbdae698f9c0e0d56fa4a3c970620c9
parent 7f5667b2482f7e1a8530660fbec90e1229a5bbfd
author Gerben <gerben@treora.com> 1621897161 +0200
committer Gerben <gerben@treora.com> 1622738231 +0200

Add describeCss & tests, document spec ambiguity

I tried a few css selector generators, listed here:
<https://github.com/fczbkk/css-selector-generator-benchmark>

- css-selector-generator failed when a root (= scope) is passed; see
  issue <https://github.com/fczbkk/css-selector-generator/issues/65>.

- using @mdev/finder instead gave syntax errors due to ‘export’ token.
  (perhaps because we don’t transpile dependencies; worth considering?)

- optimal-select seemed to work; whatever works is good enough for now.

I made describeCss accept an Element, not a Range, for its scope and
target, as Ranges make little sense for a CssSelector; I figured we may
want to change this in the matcher too, and perhaps more widely.