Bug 1588484 Comment 16 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Chris Peterson [:cpeterson] from comment #15)
> (In reply to Jeff Muizelaar [:jrmuizel] from comment #14)
> > Where does the "~40% of Windows users that don't have WebRender-compatible hardware" number come from?
> 
> I was wrong. After talking with Jim Mathies, the correct percentage is more like 10% (Release channel users stuck with basic compositor instead of D3D11 according to [1]). I think the "40%" number came from the number of users still on Windows 7 or 8 (about 30% of Windows Firefox users), which don't support WebRender yet.
> 
> Windows 7 and 8 not supporting WebRender will still be a potential blocker for rolling out Fission to those users.

Win7 is scheduled to get WebRender in 83. I've been on parental leave so haven't been following the Fission schedule, is it valuable to try to push that 82 to avoid blocking Fission?
(In reply to Chris Peterson [:cpeterson] from comment #15)
> (In reply to Jeff Muizelaar [:jrmuizel] from comment #14)
> > Where does the "~40% of Windows users that don't have WebRender-compatible hardware" number come from?
> 
> I was wrong. After talking with Jim Mathies, the correct percentage is more like 10% (Release channel users stuck with basic compositor instead of D3D11 according to [1]). I think the "40%" number came from the number of users still on Windows 7 or 8 (about 30% of Windows Firefox users), which don't support WebRender yet.
> 
> Windows 7 and 8 not supporting WebRender will still be a potential blocker for rolling out Fission to those users.

Win7 is scheduled to get WebRender in 83. I've been on parental leave so haven't been following the Fission schedule, is it valuable to try to push that to 82 to avoid blocking Fission?

Back to Bug 1588484 Comment 16