Re: Intent to unship: mozmm CSS unit.

2017-11-19 Thread Robert O'Callahan
I thought there was also a legitimate use-case for displaying content "life size", e.g. if you wanted to draw a ruler on a tablet. But if the CSSWG doesn't agree after all this time, just drop it I guess. (Though I think there's something slightly broken about how Web developer needs are

Re: Intent to unship: mozmm CSS unit.

2017-11-15 Thread Emilio Cobos Álvarez
On 11/15/2017 11:51 AM, Jonathan Kew wrote: > On 15/11/2017 03:32, Emilio Cobos Álvarez wrote: > >> So, I've looked through and I haven't found any related minutes (I've >> looked for minutes that mentioned "physical", of which they were many, >> but all related to physical properties and scroll

Re: Intent to unship: mozmm CSS unit.

2017-11-14 Thread Emilio Cobos Álvarez
Hi David, On 11/15/2017 02:27 AM, L. David Baron wrote: > On Sunday 2017-11-12 16:11 +0100, Emilio Cobos Álvarez wrote: >> Hi, >> >> In bug 1416564 I intend to remove the mozmm CSS unit. >> >> This unit is Mozilla-only, has no spec, and is unused in all our >> codebase (except for two tests, one

Re: Intent to unship: mozmm CSS unit.

2017-11-14 Thread L. David Baron
On Sunday 2017-11-12 16:11 +0100, Emilio Cobos Álvarez wrote: > Hi, > > In bug 1416564 I intend to remove the mozmm CSS unit. > > This unit is Mozilla-only, has no spec, and is unused in all our > codebase (except for two tests, one of those which tests the unit itself). > > This unit was

Re: Intent to unship: mozmm CSS unit.

2017-11-12 Thread Emilio Cobos Álvarez
Also, another thought I just had about this unit: Probably if we don't unship it, then privacy.resistFingerPrinting should do something about it, since it allows to calculate the DPI of the screen trivially using CSSOM accessors. Filed bug 1416574. ___

Re: Intent to unship: mozmm CSS unit.

2017-11-12 Thread Gijs Kruitbosch
On 12/11/2017 16:36, Emilio Cobos Álvarez wrote: On 11/12/2017 05:14 PM, Xidorn Quan wrote: I doubt if there is anything changed since then (except that we still haven't pushed this on csswg), so maybe we still shouldn't remove it. I'm definitely ok with adding something like that if there's

Re: Intent to unship: mozmm CSS unit.

2017-11-12 Thread Gijs Kruitbosch
On 12/11/2017 16:56, Gijs Kruitbosch wrote: because layout already adjusts some (but not all!) sizes to align to device pixels For reference: https://bugzilla.mozilla.org/show_bug.cgi?id=477157 and friends. ~ Gijs ___ dev-platform mailing list

Re: Intent to unship: mozmm CSS unit.

2017-11-12 Thread Emilio Cobos Álvarez
On 11/12/2017 05:14 PM, Xidorn Quan wrote: > IIRC, we have discussed unshipping this somewhere before we added its > support to stylo (maybe the Taipei meeting this year?) and dbaron said > that mozmm provides an ability to size something based on physical size > which is not directly possible

Re: Intent to unship: mozmm CSS unit.

2017-11-12 Thread Xidorn Quan
On Mon, Nov 13, 2017, at 02:11 AM, Emilio Cobos Álvarez wrote: > Hi, > > In bug 1416564 I intend to remove the mozmm CSS unit. > > This unit is Mozilla-only, has no spec, and is unused in all our > codebase (except for two tests, one of those which tests the unit > itself). > > This unit was

Intent to unship: mozmm CSS unit.

2017-11-12 Thread Emilio Cobos Álvarez
Hi, In bug 1416564 I intend to remove the mozmm CSS unit. This unit is Mozilla-only, has no spec, and is unused in all our codebase (except for two tests, one of those which tests the unit itself). This unit was introduced experimentally in bug 537890, our browser chrome code used it in bug