Extend bug 1764354 to apply to content as well.
Categories
(Core :: SVG, task)
Tracking
()
People
(Reporter: emilio, Assigned: emilio)
References
Details
(Keywords: dev-doc-complete)
Attachments
(3 files)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
873 bytes,
patch
|
diannaS
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
749 bytes,
patch
|
diannaS
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Assignee | ||
Comment 1•3 years ago
|
||
As per discussion in https://github.com/w3c/csswg-drafts/issues/7213.
Updated•3 years ago
|
Comment 6•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/33fbecca098c
https://hg.mozilla.org/mozilla-central/rev/f31efc2a9229
https://hg.mozilla.org/mozilla-central/rev/34f9bcdd17ff
Assignee | ||
Comment 8•3 years ago
|
||
Approval Request Comment
[Feature/Bug causing the regression]: none
[User impact if declined]: We don't want to ship this feature as-is. It needs a minor change in bug 1782595, but since we also need to extend the feature to iframes (bug 1782596), it seems probably wiser to just turn it off in 104 and ship both things at the same time.
[Is this code covered by automated tests?]: yes
[Has the fix been verified in Nightly?]: N/A
[Needs manual test from QE? If yes, steps to reproduce]: No
[List of other uplifts needed for the feature/fix]: None
[Is the change risky?]: No
[Why is the change risky/not risky?]: Prefs off feature to go to the previous behavior for at least one more cycle.
[String changes made/needed]: No
Comment 9•3 years ago
|
||
Comment on attachment 9288036 [details] [diff] [review]
Turn this off on beta, for now
Approved for 104.0b6
Comment 10•3 years ago
|
||
bugherder uplift |
Updated•3 years ago
|
Comment 11•3 years ago
|
||
To address an expected failure https://treeherder.mozilla.org/logviewer?job_id=386266022&repo=mozilla-beta&lineNumber=5747
Comment 12•3 years ago
|
||
FF105 Docs for this can be tracked in https://github.com/mdn/content/issues/19449. We'll start a little closer to the release.
Emilio, is there a way of knowing when the discussion of the WG will make it into the specification? That way I can create a subfeature for this with a link to the specification in the browser compatibility data.
Updated•3 years ago
|
Assignee | ||
Comment 13•3 years ago
|
||
Well, someone needs to send a PR to the specification, or the editors will make the edits themselves. So no great way to know.
Comment 14•3 years ago
|
||
Thanks Emilio. I'm not sure an intent to accept this update to the spec is far enough along to mark this as "standard" in the browser compatibility data. So I'll probably have to mark as non-standard. If you create or see said PR can you please ping me.
Updated•2 years ago
|
Comment 15•2 years ago
|
||
I've removed the dev-docs-needed
keyword as there is documentation added for this in the following tracking issue on GitHub.
Updated•2 years ago
|
Description
•