mdn / mdn/browser-compat-data

api.Element.animationend_event - Element does not include event handlers, but HTML/MathML/SVGElement does

Open
#17,127 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data:api
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

Description

What type of issue is this?

Other

What information was incorrect, unhelpful, or incomplete?

#16531 demixed animation events from GlobalEventHandlers to Element, but Element does not directly include GlobalEventHandlers.

https://html.spec.whatwg.org/multipage/dom.html#htmlelement

HTMLElement includes GlobalEventHandlers;

https://w3c.github.io/mathml-core/#dom-and-javascript

MathMLElement includes GlobalEventHandlers;

https://svgwg.org/svg2-draft/types.html#InterfaceSVGElement

SVGElement includes GlobalEventHandlers;
What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Internet), Firefox, Safari

What did you expect to see?

Technically it does not exist on Element, so I'd say it should exist on each element?

That said, every sub-interface of Element include GlobalEventHandlers, but there's still a way to create an instance of Element, see below.

Did you test this? If so, how?

document.createElementNS("abc", "foo").onanimationcancel

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

I see the urge to ignore such edge case, since otherwise quite a lot of data should be duplicated to three interfaces. Perhaps this is a chance to change the spec?

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/Element/animationend_event

MDN metadata
MDN page report details
  • Query: api.Element.animationend_event
  • Report started: 2022-07-26T01:45:17.273Z

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the api.Element.animationend_event entry and compare it with the linked HTML, MathML, and SVG specifications and the MDN page. Determine whether the event should remain on Element or be represented on the three sub-interfaces, then update the compatibility data consistently and verify the resulting API documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
documentation, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.