Re: Intent to Ship: Display Cutout & CSS Environment Variables

On 6/21/18 7:30 PM, Becca Hughes wrote:
> Risks
> 
> Interoperability and Compatibility
> 
> Edge: No signals
> 
> Firefox: No signals

FWIW, signals from Mozilla's side are negative I'd say, at least until 
there's a proper spec and agreement on which environment variables 
should people implement and ship, and that they all have gone through 
the relevant privacy review, the same way new CSS properties go through 
a process to get in a spec.

The fact that all the variable names are not listed anywhere would make 
it pretty hard for others to implement and keep up with changes. We'd 
need to keep track of the WebKit and Blink repos, and figure out when 
they or you ship more of these. I don't think such a situation would be 
tractable. Relevant links are [1] and [2] in this regard.

On the other hand, we do have a bug on file to implement[3], and 
potential use-cases (see dependent bugs). Plus, our mobile team would 
also love it, I'd suspect.

But I don't think we'd ship this without those concerns addressed, and 
I'd be really sad if Blink did that.

  -- Emilio

[1]: 
https://groups.google.com/d/msg/mozilla.dev.tech.layout/UpzhcwaRyrM/J5sv7pfXAAAJ
[2]: 
https://groups.google.com/a/chromium.org/d/msg/blink-dev/ZS1mEwvN-5E/rQvcSx0fAgAJ
[3]: https://bugzilla.mozilla.org/show_bug.cgi?id=1462233

-- 
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/260a26b2-ee83-97e9-1df2-cb7df85e8cfc%40mozilla.com.