mdn / mdn/browser-compat-data

api.SVGElement.error_event - The event is fired only on image in implementations

Open
#17,456 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:multiple 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?

Missing compatibility data

What information was incorrect, unhelpful, or incomplete?

The table states only about a general error event, but this doesn't say on which element this event is supported.
Per specs the error event should fire for all structurally external element, so ‘foreignObject’, ‘image’, ‘script’ and ‘use’. This event is also supposed to bubble.

UAs only fire it on <image> and it doesn't even bubble (Chromium does also fire script errors on the root <svg> in standalone documents).

What browsers does this problem apply to, if applicable?

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

What did you expect to see?

Maybe a list like

error bubbles: (none)
error on <image>: (all)
error on <use>: (none)
error on <foreignObject>: (none)
error on <script>: (none)
error on <svg> for script errors: (Chromium only)

Did you test this? If so, how?

https://jsfiddle.net/6b0eLg13/

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?

No response

MDN URL

https://developer.mozilla.org/en-US/docs/Web/API/SVGElement/error_event

MDN metadata
MDN page report details
  • Query: api.SVGElement.error_event
  • Report started: 2022-08-18T01:58:28.124Z

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 MDN SVGElement/error_event page, the SVG specification links, and the provided JSFiddle to verify the listed browser behavior. Update the compatibility data so support distinguishes bubbling and the image, use, foreignObject, script, and svg cases described in the report, then run the repository's data validation checks.

Written by the indexing model from the issue text.

Assessment

Tech stack
json
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.