Closed Bug 1133174 Opened 9 years ago Closed 1 year ago

disable SVGGraphicsElement.{nearest,farthest}ViewportElement in nightlies and early beta

Categories

(Core :: SVG, task)

task

Tracking

()

RESOLVED FIXED
Tracking Status
firefox109 --- fixed

People

(Reporter: heycam, Assigned: longsonr)

References

Details

(Keywords: dev-doc-complete, site-compat)

Attachments

(1 file, 2 obsolete files)

Attached patch patch (obsolete) — Splinter Review
The SVG WG resolved to remove SVGGraphicsElement.{nearest,farthest}ViewportElement due to lack of use.

r?longsonr for the removal, r?bz for the IDL change DOM peer review.
Attachment #8564478 - Flags: review?(longsonr)
Attachment #8564478 - Flags: review?(bzbarsky)
Keywords: dev-doc-needed
Comment on attachment 8564478 [details] [diff] [review]
patch

r=me, but again what is the data showing lack of use?
Attachment #8564478 - Flags: review?(bzbarsky) → review+
Keywords: site-compat
Type: defect → task
Severity: normal → S3
Assignee: nobody → longsonr
Status: NEW → ASSIGNED
Keywords: parity-chrome
Attachment #8564478 - Attachment is obsolete: true
Attachment #9306682 - Attachment is obsolete: true
Keywords: parity-chrome
Pushed by longsonr@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/b386e45bfee7
Disable SVGGraphicsElement.{nearest,farthest}ViewportElement in early beta r=emilio
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/37350 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot

Why leave-open on this bug? If it's to disable by default later, it would be easier to track if a new bug was opened for that that depends on this one.

Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Keywords: leave-open
Resolution: --- → FIXED
Summary: remove SVGGraphicsElement.{nearest,farthest}ViewportElement → disable SVGGraphicsElement.{nearest,farthest}ViewportElement in nightlies and early beta

FF109 docs for this can be tracked in https://github.com/mdn/content/issues/22737#issuecomment-1369426580

@Robert,

  1. Doesn't disabling this in nightly/early beta mean it is still present in the release version? So when 109 is released it will "become available" in that version? FMI What's the point in that?
  2. These are not documented in MDN or present in the compatibility data. It seems to me that since it was removed for being unused there is no point adding any information about these at this point - not even a release note change. Does that seem reasonable to you?
Flags: needinfo?(longsonr)
  1. The point is to see whether we can remove these functions completely without breaking anything. I hope we'll change the pref to false by default in some version later this year and then remove the feature completely after that.
  2. The functions were removed from the SVG 2 specification. We might say in a release note that we intend to remove them completely in a future release. They do show deprecated warnings now if they are used, even in a release version.
Flags: needinfo?(longsonr)

Thanks Robert. Agreed! Release note done.

Blocks: 1879773
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: