| 05:19 | <sideshowbarker> | Is the spec definition of “interactive content” https://html.spec.whatwg.org/multipage/dom.html#interactive-content intended to include the SVG `a` element, or instead only intended to include the HTML `a` element? |
| 05:23 | <sideshowbarker> | I realize the definition _links_ only to the HTML element, but I wonder whether any implementations have assumed the SVG `a` element should be included. |
| 05:26 | <sideshowbarker> | Regardless, _should_ we explicitly include “the `a` element in the SVG namespace” in that definition of “interactive content”? |
| 06:38 | <annevk> | ljharb: you can't create a blank one |
| 06:41 | <annevk> | sideshowbarker: where does that definition have an impact on implementations? But yeah, generally I think <a> and svg:a should be treated the same. |
| 07:22 | <sideshowbarker> | sideshowbarker: where does that definition have an impact on implementations? But yeah, generally I think <a> and svg:a should be treated the same. summary element, when deciding whether an activation event somewhere inside the summary should toggle its details |
| 07:29 | <sideshowbarker> | And https://searchfox.org/wubkat/source/Source/WebCore/html/HTMLLabelElement.cpp#124 is one other existing place I could find in the WebKit sources at least |
| 07:33 | <sideshowbarker> | It seems like that rightly should be considering the SVG `a` element too — but that `if (is<HTMLElement>(it) && downcast<HTMLElement>(*it).isInteractiveContent())` won't catch it. |
| 07:38 | <annevk> | Yeah, hmm. Is svg:a the only interactive element outside of HTML? |
| 07:40 | <sideshowbarker> | Yeah, hmm. Is svg:a the only interactive element outside of HTML? |
| 07:41 | <sideshowbarker> | Nothing else interactive in SVG, as far as I can see, and nothing at all in MathML that's interactive |
| 07:58 | <annevk> | sideshowbarker: cool, I think we should just change that in the HTML Standard then, just like we already treat SVGImageElement special in a couple of places |
| 07:59 | <sideshowbarker> | sideshowbarker: cool, I think we should just change that in the HTML Standard then, just like we already treat SVGImageElement special in a couple of places |
| 15:17 | <annevk> | 1 << 31 + unsigned long = positive integer? The final bit of https://webidl.spec.whatwg.org/#abstract-opdef-converttoint is tricky. |
| 22:40 | <ljharb> | ljharb: you can't create a blank one about:blank works great in theory. but you're right, which is why maybe the better solution for my use cases is some kind of URL.from(object) API |