-
Notifications
You must be signed in to change notification settings - Fork 132
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement #60
Comments
I don't think However, it may be preferable to define it within the DOM specs as a "mixin" interface that can then be implemented by both Anyone want to take responsibility for looking into this possibility with HTML WG and WHATWG? |
There is now a PR for this and blur/focus/tabindex in HTML whatwg/html#3543 |
To be clear, we're moving this to a mixin in HTML (tests pending) that will still be included on SVGElement, rather than moving it to Element. |
This exposes dataset, tabIndex, focus(), and blur() on SVG elements. It also does away with NoncedElement. Tests: web-platform-tests/wpt#10110 and web-platform-tests/wpt#10149 (dataset tests for SVG already exist). Fixes #3471 and fixes w3c/svgwg#60.
In the above referenced commit I said that it fixed this issue, but I guess what still remains is that you need to remove |
Yep, marking this as "needs edits" and updating the title to match the chosen solution. |
This brings up again the issue of whether SVG wants to link normatively to WHATWG interfaces; we currently reference W3C versions. With the new WHATWG royalty commitments, it's probably less of an issue, but still a little messy & political to make the change. I'll file an issue on W3C/html to ask if they can mirror the change, but not sure how long that might take. |
We would appreciate it if in working collaboratively with us, you did not then turn around and request that another group copy our work so that you can proceed to ignore our work in your spec :(. |
The Working Group just discussed The full IRC log of that discussion<BogdanBrinza> topic: (Revisiting) Move dataset & other shared IDL attributes from SVGElement to HTMLOrSVGElement<BogdanBrinza> GitHub: https://github.com//issues/60 <BogdanBrinza> dstorey: SVG 2.0 current draft already links to the Fetch specification so we won't make things worse in PR if we add another one <BogdanBrinza> Resolution: Link to WHATWG spec now to resolve github.com//issues/60, while Liam is confirming this with W3C |
This exposes dataset, tabIndex, focus(), and blur() on SVG elements. It also does away with NoncedElement. Tests: web-platform-tests/wpt#10110 and web-platform-tests/wpt#10149 (dataset tests for SVG already exist). Fixes whatwg#3471 and fixes w3c/svgwg#60.
This exposes dataset, tabIndex, focus(), and blur() on SVG elements. It also does away with NoncedElement. Tests: web-platform-tests/wpt#10110 and web-platform-tests/wpt#10149 (dataset tests for SVG already exist). Fixes whatwg#3471 and fixes w3c/svgwg#60.
The current draft of the SVG spec defines
dataset
attribute on the SVGElement interface while HTML 5 spec defines it on the HTMLElement interface.Is there any particular reason why
dataset
couldn't be defined just once on theElement
interface like other similar attributes such asclassList
?The text was updated successfully, but these errors were encountered: