- From: Anne van Kesteren <notifications@github.com>
- Date: Fri, 16 Mar 2018 05:32:45 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 16 March 2018 12:33:08 UTC
Looking into #457 for ranges, it seems that ranges can point to `Attr` nodes in all browsers, but it never seems useful. Is it worth trying to make this throw? If not, at least as far as ranges are concerned, an attribute's `<a for=Node>length</a>` is 0, similar to doctypes, meaning the following throws: ```html .<body x=fd><Script> r = new Range() r.setStart(document.body.getAttributeNode("x"), 0); r.setEnd(document.body.getAttributeNode("x"), 1); </script> ``` Whether or not we keep this I guess I should also look at the various other Range members and how they interact with attribute nodes and ensure the test suite covers it. cc @smaug---- -- 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/607
Received on Friday, 16 March 2018 12:33:08 UTC