api.SVGPointList - cannot contain DOMPoint in browsers
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/SVGPointList
What specific section or headline is this issue about?
No response
What information was incorrect, unhelpful, or incomplete?
The SVGPointList interface represents a list of DOMPoint objects.
If I try to add a DOMPoint to SVGPointList in Firefox, I get this error:
Uncaught TypeError: SVGPointList.insertItemBefore: Argument 1 does not implement interface SVGPoint.
What did you expect to see?
I'm not sure... The issue is quite subtle. SVGPointList accepting DOMPoints is an SVG 2 feature, while SVG 2 is not in a very good place in general. It's definitely not surprising that some SVG 2 feature is missing from browsers. I think that the article should either list the gotchas or document both SVG 1.1 and SVG 2.0 behaviors, I'm not experienced enough with MDN practices to decide what's the proper way forward.
Do you have any supporting links, references, or citations?
No response
Do you have anything more you want to share?
No response
MDN metadata
Page report details
- Folder:
en-us/web/api/svgpointlist - MDN URL: https://developer.mozilla.org/en-US/docs/Web/API/SVGPointList
- GitHub URL: https://github.com/mdn/content/blob/main/files/en-us/web/api/svgpointlist/index.md
- Last commit: https://github.com/mdn/content/commit/43a8839abdfb01d4388f11a028582bec4e7ead18
- Document last modified: 2025-06-08T10:11:23.000Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with files/en-us/web/api/svgpointlist/index.md and compare its DOMPoint statement with the SVG 1.1 and SVG 2 behavior described in the issue. Confirm the relevant browser behavior, then update the article so the documented behavior and compatibility caveats are accurate; done means the DOMPoint guidance no longer contradicts Firefox.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation, web-dev
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100