On Thu, Jul 11, 2019 at 8:47 AM Jeff Muizelaar <jmuizel...@mozilla.com> wrote:
> I believe there's some precedent for this. I have a vague memory of a > browser which didn't have working 3d transforms if not run with a GPU. > Further, I'm not sure that having a broken backdrop filter is that > much worse an experience than the performance degradation that comes > from disabling GPU acceleration. That being said, I agree it's not an > ideal situation. > Sites may rely on the filter in ways that could affect legibility of content. For instance, text on top of content that has a background blur. Definitely not ideal. > I think we can probably postpone making a decision about this until we > have a working implementation on top of WebRender. We'll then be in a > better spot to evaluate the work needed to make this work with > non-WebRender vs waiting for WebRender everywhere vs the weirdness of > partially shipping it as proposed here. > I agree with this plan of attack. The WR implementation can help us assess the level-of-work and timing for the non-WR implementation (vs waiting for WR to ship everywhere). Which was essentially the plan all along anyway :) That said, I think the last option (partial shipping) is not really an option at all. Sean _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
