Missing svg features data
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
missing data for svg
What browsers does this problem apply to, if applicable?
No response
What did you expect to see?
add data for svg
Did you test this? If so, how?
-
api.SVGViewElement.zoomAndPan
- non-standard
- deprecated
-
api.SVGGraphicsElement.farthestViewportElement
- non-standard
- #25258
-
api.SVGGraphicsElement.nearestViewportElement
- non-standard
- #25258
-
svg.elements.marker.preserveAspectRatio
- api.SVGMarkerElement.preserveAspectRatio existed
- #25256
-
svg.elements.pattern.viewBox
- api.SVGPatternElement.viewBox existed
- #25255
-
svg.elements.pattern.preserveAspectRatio
- api.SVGPatternElement.preserveAspectRatio existed
- #25255
-
svg.elements.pattern.requiredExtensions
- api.SVGPatternElement.requiredExtensions existed
- non-standard
- #25196
-
api.SVGPatternElement.systemLanguage
- non-standard
- #25196
-
api.SVGPatternElement.requiredExtensions
- non-standard
- #25196
-
svg.elements.script.crossorigin
- api.SVGScriptElement.crossOrigin existed
-
svg.{feBlend,feColorMatrix,feComponentTransfer,feComposite,feConvolveMatrix,feDiffuseLighting,feDisplacementMap,feDropShadow,feFlood,feGaussianBlur,feImage,feMerge,feMorphology,feOffset,feSpecularLighting,feTile,feTurbulence}.{width,height}
-
svg.{feBlend,feColorMatrix,feComponentTransfer,feComposite,feConvolveMatrix,feDiffuseLighting,feDisplacementMap,feDropShadow,feFlood,feFuncA,feFuncB,feFuncG,feFuncR,feGaussianBlur,feImage,feMerge,feMergeNode,feMorphology,feOffset,feSpecularLighting,feTile,feTurbulence}.{x,y}
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
No response
MDN metadata
No response
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
Review the existing SVG compatibility entries in the dataset and the referenced issues #25255, #25256, #25196, and #25258. Add the missing entries and verify their browser support metadata, including the non-standard and deprecated labels. Done means every feature listed in the issue has corresponding compatibility data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100