On 02/01/2016 11:46 PM, Justin Dolske wrote:
On 2/1/16 9:51 AM, Kartikaya Gupta wrote:
Oh, I should also mention that currently many (if not all) Windows
touchscreen devices have e10s disabled by default, because a
touchscreen seems to trigger the accessibility code which disables
e10s. And if e10s is disabled, APZ is disabled, which means no APZ
touch scrolling.
I assume there's a bug(s) on file for making e10s/a11y work right on touch
devices?
Looking at the TOUCH_ENABLED_DEVICE telemetry probe, while touch devices are a
fairly small segment of the overall userbase (~2%, for beta 44), it's
significantly higher on what I'd expect to be modern hardware (7.4% of Windows
10 users, 6.9% for Win8.1).
Justin
That 7.4% is significantly *lower* than what I'd expect for modern hardware. I
would have expected something like 25% or higher, based on the
laptops being sold in Finland.
But anyhow, 7.4% is definitely high enough that we should make the a11y work a top priority thing, like having some small group of people working only
on that or something.
(unfortunately the first approach for e10s+a11y didn't seem to have quite
worked.)
-Olli
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
