mdn / mdn/browser-compat-data

svg.elements.a - Missing "target="_blank" implies rel="noopener" behavior" data

Open
#27,807 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

For HTML's a and area elements there's data to show when implicit noopener was added. But the same is not true for SVGAElement.

What browsers does this problem apply to, if applicable?

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

What did you expect to see?

I expected to see data on whether Firefox supports this behaviour. (Chrome should also support this as of 135 but that data is entirely missing).

Safari despite supporting rel and relList on SVG doesn't seem to actually use the values for anything. So it currently doesn't support this.

Did you test this? If so, how?

No.

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/SVG/Reference/Element/a

MDN metadata
MDN page report details
  • Query: svg.elements.a
  • Report started: 2025-09-09T20:47:12.305Z

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 svg.elements.a query and compare the missing entry with the existing HTML a and area compatibility data. Verify the reported Firefox, Chrome 135, and Safari behavior, then update the browser compatibility data to represent implicit rel="noopener" support for SVG a.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.