Hi Ehsan,

Currently, the plan is to develop this feature behind a pref flag that will
be off by default. We haven't decided the best way forward for enabling
this feature by default yet. We have two possible options:
 1. Add backdrop filter support to the other render backends.
 2. Rely on an @supports media query to determine if backdrop-filter is
supported (this would check for the backdrop-filter pref flag and check if
WebRender is enabled). If we choose this route, we need to remove any
dynamic fallbacks to the software renderer that may occur when using
backdrop-filter. Currently WebRender does not support all SVG filters, so
these would need to be fully implemented for this approach to work.

>  * Do we have other web-exposed features that are only supported when
WebRender is enabled?

I don't believe we have any other web-exposed features only supported by
WebRender at the moment.

> * How do we plan to communicate to web developers (who may not
necessarily know/care what WebRender is) where this feature is usable?

This is a good thing to keep in mind when determining the right approach.
If we decide to implement backdrop-filter on all backends, this won't be an
issue; otherwise, if we go with approach 2, we would need to tell web
developers to rely on the @supports media query.

> * What happens to the DevTools integration a) when WebRender is disabled
on the target Firefox instance, and b) when WebRender is disabled on the
target Firefox instance but enabled on the host instance (e.g. when
debugging Fennec on Windows with the right NVIDIA GPU driver).

Currently, DevTools only checks if the backdrop-filter pref is enabled and
doesn't check if WebRender is enabled. If we decide on approach 2, we would
need to check for the cases that you mentioned.

Thanks,
Connor


On Fri, Jul 5, 2019 at 7:23 AM Ehsan Akhgari <ehsan.akhg...@gmail.com>
wrote:

> On Mon, Jul 1, 2019 at 8:54 PM Connor Brewster <cbrews...@mozilla.com>
> wrote:
>
>> Platform coverage: All platforms using the Gecko rendering engine
>> (WebRender enabled only)
>>
>> Target release: Firefox 71 (WebRender enabled only)
>>
>> DevTools bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1561060
>>
>
> Hi Connor,
>
> Since this feature is only enabled based on WebRender being enabled, I
> have a few questions for you:
>
> * Do we have other web-exposed features that are only supported when
> WebRender is enabled?
>
> * How do we plan to communicate to web developers (who may not necessarily
> know/care what WebRender is) where this feature is usable?
>
> * What happens to the DevTools integration a) when WebRender is disabled
> on the target Firefox instance, and b) when WebRender is disabled on the
> target Firefox instance but enabled on the host instance (e.g. when
> debugging Fennec on Windows with the right NVIDIA GPU driver).
>
> Thanks,
> --
> Ehsan
>
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to