Intent to Deprecate and Remove: SVGSVGElement.pixelUnitToMillimeterX and friends

[Philip Jägenstedt]

Primary eng (and PM) emails

phi...@opera.com

Summary

Remove SVGSVGElement.pixelUnitToMillimeterX, pixelUnitToMillimeterY, screenPixelToMillimeterX and screenPixelToMillimeterY.

Motivation

These were in SVG 1.1 put have been removed:

http://www.w3.org/TR/SVG11/struct.html#InterfaceSVGSVGElement

http://www.w3.org/TR/SVG2/struct.html#InterfaceSVGSVGElement

These properties all return the constant 0.2645833194255829 on all platforms, so they don't do what their names suggest.

Compatibility Risk

This was implemented (by eseidel@) in WebKit in 2005:

https://bugs.webkit.org/show_bug.cgi?id=3250

http://trac.webkit.org/changeset/9636

(The original code tried to actually return a truthful value.)

Risk seems low, but only because usage is so low.

Alternative implementation suggestion for web developers

Use the constant 0.2645833194255829, which means assuming 96 PPI, and simplify.

Usage information from UseCounter

https://www.chromestatus.com/metrics/feature/timeline/popularity/774

https://www.chromestatus.com/metrics/feature/timeline/popularity/775

https://www.chromestatus.com/metrics/feature/timeline/popularity/776

https://www.chromestatus.com/metrics/feature/timeline/popularity/777

Usage is around 0.0001%, sometimes rounding to zero.

OWP launch tracking bug

Add crbug.com/537177 link to an OWP launch tracking bug.

Entry on the feature dashboard

https://www.chromestatus.com/feature/5478103916740608

Requesting approval to remove too?

Yes, when usage is this low nobody will see the deprecation message anyway, so all we can reasonably do is to try the removal and see what happens.

[Jochen Eisinger]

lgtm

[Chris Harrelson]

LGTM2

lgtm

To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

[Dimitri Glazkov]

LGTM3.