Bugzilla

(In reply to Benjamin De Cock from comment #85)
> Any rough estimate on when both webrender and backdrop-filter will be enabled by default? :)

webrender:  already enabled by default for some fraction of our userbase, though I believe there's some fraction that will never be able to have it on by default because of graphics hardware limitations.

backdrop-filter: not sure. it's complicated by the fact that it's only implemented for webrender right now, so we can't just turn on support for it in our css parser without "lying" on non-webrender configurations. (And there's a decent amount of work involved in implementing it on other backends; and on the other hand, we could theoretically just make the CSS parser only recognize backdrop-filter if webrender is enabled, but that's complicated too, because webrender can also get transparently turned off in the presence of some types of content, I think.)  Anyway, that's tracked in 1578503, so you can follow along there.

(In reply to Benjamin De Cock from comment #85)
> Any rough estimate on when both webrender and backdrop-filter will be enabled by default? :)

webrender:  already enabled by default for some fraction of our userbase (and I think (?) we're slowly ramping this up), though I believe there's some fraction that will never be able to have it on by default because of graphics hardware limitations.

backdrop-filter: not sure. it's complicated by the fact that it's only implemented for webrender right now, so we can't just turn on support for it in our css parser without "lying" on non-webrender configurations. (And there's a decent amount of work involved in implementing it on other backends; and on the other hand, we could theoretically just make the CSS parser only recognize backdrop-filter if webrender is enabled, but that's complicated too, because webrender can also get transparently turned off in the presence of some types of content, I think.)  Anyway, that's tracked in 1578503, so you can follow along there.

(In reply to Benjamin De Cock from comment #85)
> Any rough estimate on when both webrender and backdrop-filter will be enabled by default? :)

webrender:  already enabled by default for some fraction of our userbase (and I think (?) we're slowly ramping this up), though I believe there's some fraction that will never be able to have it on by default because of graphics hardware limitations.

backdrop-filter: not sure. it's complicated by the fact that it's only implemented for webrender right now, so we can't just turn on support for it in our css parser without "lying" on non-webrender configurations. (And there's a decent amount of work involved in implementing it on other backends; and on the other hand, we could theoretically just make the CSS parser only recognize backdrop-filter if webrender is enabled, but that's complicated too, because webrender can also get transparently turned off in the presence of some types of content, I think.)  Anyway, that's tracked in bug 1578503, so you can follow along there.