[whatwg/dom] Introduce a StaticRange constructor (#590)

Somehow `StaticRange` got added to browsers without the TAG noting the lack of a constructor.  #589 adds `StaticRange` to the DOM Standard.

The proposal by @garykac in https://w3c.github.io/staticrange/index.html#interface-staticrange seems reasonable. You require a dictionary to be passed specifying all the bits.

One question is whether those bits should be validated as https://github.com/w3c/staticrange/issues/13 suggests or whether we should allow any inputs and just pass them through. After all, you need to validate a `StaticRange` object whenever you use it, so why do it here as well? (Do we have any APIs yet that take `StaticRange` objects?)

It's not entirely clear to me what the tradeoffs are here.

cc @rniwa @johanneswilm @bzbarsky @dstorey

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/590