Remove SVG elements <hatch> and <hatchpath> - #15856
Merged
Merged
Conversation
3 tasks
sideshowbarker
approved these changes
Apr 18, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Remove SVG elements
<hatch>and<hatchpath>which are non-standard and as far as I know were never implemented by any browser.Test results and supporting details
SVG elements
<hatch>and<hatchpath>were removed from SVG spec in 2018 with statement "Deferred hatch and hatchpath elements to a future version of SVG."MDN has a test/demo here. The demo does not work, of course.
According to my personal (not informed) opinion, these elements are not likely to be ever implemented, since developers already can create hatch patterns with
<path>,<pattern>and<mask>. Perhaps, we could ping someone knowledgeable?Related issues