remove requiredFeatures from SVGTests
Categories
(Core :: SVG, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: longsonr, Assigned: longsonr)
References
Details
(Keywords: site-compat)
Attachments
(1 file, 4 obsolete files)
They've been removed from SVG 2
Assignee | ||
Comment 1•8 years ago
|
||
Assignee | ||
Comment 2•8 years ago
|
||
Comment on attachment 8781350 [details] [diff] [review] WIP - still needs various tests to be fixed or removed Should I remove hasExtension() from SVGTests here or in another bug?
Comment 3•8 years ago
|
||
Comment on attachment 8781350 [details] [diff] [review] WIP - still needs various tests to be fixed or removed Review of attachment 8781350 [details] [diff] [review]: ----------------------------------------------------------------- I found bug 1295404 for removing hasExtension(), but I guess I overlooked sending that mail. In that bug you mentioned we should do this removal behind a pref, presumably because we would be the first ones removing this. (I just checked, and Chrome/Safari/Edge all still expose SVGTests.requiredFeatures.) From foolip's comment in https://bugs.chromium.org/p/chromium/issues/detail?id=635420 it sounds like the Blink use counter is sufficiently low for SVGTests in general. And my gut feeling is that it's safe. But if you think we should still put this behind a pref for now, then I'm still in favour of making hasFeature() just return true all the time (which would solve bug 1216893's issue). We should probably still send an intent to unimplement, either way.
Assignee | ||
Comment 4•8 years ago
|
||
bug 1295404 is this bug. I think I'll morph this into HasFeature to return true. Then the other bug (whatever it is) can remove it.
Comment 5•8 years ago
|
||
Oops, bug 1133175 is for hasExtension.
Updated•7 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Assignee | ||
Comment 7•5 years ago
|
||
Comment 8•5 years ago
|
||
Chrome has already removed all interfaces in svg/historical.html
: https://wpt.fyi/results/svg/historical.html
We probably should also remove the remaining 3 interfaces.
Assignee | ||
Comment 9•5 years ago
|
||
Well I'm not sure...
useCurrentView is actually pretty useful to us for our own tests. I'd rather leave it as it's hard to test fragment identifiers otherwise.
getTransformToElement is pretty harmless, there's a polyfill somewhere that adds it back.
w3c are still talking about SVGZoomAndPan - https://lists.w3.org/Archives/Public/www-svg/2019Jun/0014.html maybe that will end up being removed altogether since that one really is useless as we don't send any zoom/pan events.
So I'd rather fix other things really.
Assignee | ||
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
Assignee | ||
Comment 12•5 years ago
|
||
Assignee | ||
Comment 13•5 years ago
|
||
Assignee | ||
Comment 14•5 years ago
|
||
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 15•5 years ago
|
||
https://www.w3.org/TR/SVG2/struct.html#ConditionalProcessingOverview
Previous versions of SVG included a third conditional processing attribute, requiredFeatures. This was intended to allow authors to provide fallback behavior for user agents that only implemented parts of the SVG specification. Unfortunately, poor specification and implementation of this attribute made it unreliable as a test of feature support.
Chrome removed it some time ago.
bzbarsky for the webidl change
Comment 16•5 years ago
|
||
Chrome removed it some time ago.
Does Safari support it?
Comment 17•5 years ago
|
||
Nevermind, found https://wpt.fyi/results/svg/historical.html?label=master&label=experimental&q=svg%2Fhistorical.html which shows Safari supports it.
Updated•5 years ago
|
Comment 18•5 years ago
|
||
Pushed by longsonr@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/ba32151f8fc1 Remove requiredFeatures from SVGTests r=dholbert r=bzbarsky
Comment 19•5 years ago
|
||
bugherder |
Comment 20•5 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.dev/en-CA/docs/2019/requiredfeatures-has-been-removed-from-some-svg-interfaces/
Description
•