- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Sep 2019 22:00:47 +0000
- To: public-svg-issues@w3.org
With respect to the section quoted in https://github.com/w3c/svgwg/issues/741#issuecomment-533970957, we already have an open issue for fixing that language (#467). But the window event handlers are separate. HTML [exposes them on body/frameset](https://html.spec.whatwg.org/multipage/webappapis.html#event-handlers-on-elements,-document-objects,-and-window-objects:event-handlers-6) (including as markup attributes) as well as the window DOM object. [SVG 1.1 defined a list of "document-level event attributes" that can only be specified on `<svg>`](https://www.w3.org/TR/SVG11/script.html#DocumentEvents). However, many items on that list are now global events in HTML & are supported on all elements. The only crossover between the two lists is "onunload", although the SVG version was linked to a unique "SVGLoad" event that we've since removed. Quick testing today, neither Chrome nor Firefox seem to support `onunload` on `<svg>` elements (as either an IDL value or an attribute), nor do they support any of the newer window event handlers. So maybe we can just match reality and drop any attribute version of these handlers? That means you couldn't set them from markup in a standalone scripted SVG file, but do you really need to? I don't think anyone's ever complained about them missing… -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/741#issuecomment-534302316 using your GitHub account
Received on Monday, 23 September 2019 22:00:48 UTC