Closed Bug 1244449 Opened 8 years ago Closed 8 years ago

Is e10s always disabled on windows 10 by bug 1163004?

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: tetsuharu, Unassigned)

Details

environment
-----------
- Nightly, x64, buildid: 20160130030240
- Windows 10 x64, ver.1511, build10686.71


description
------------

On my windows 10 laptop, e10s is "disabled by accessibility tools". But I don't introduce any a11y support tools...

And I found the bug 1163004 which is always enables a11y feature on windows 10.
So does the combinations of bug 1198459 and bug 1163004 cause always to disable e10s on Windows 10?


I'm sorry if this assumption is incorrect.
(In reply to Tetsuharu OHZEKI [UTC+9] from comment #0)
> environment
> -----------
> - Nightly, x64, buildid: 20160130030240
> - Windows 10 x64, ver.1511, build10686.71
> 
> 
> description
> ------------
> 
> On my windows 10 laptop, e10s is "disabled by accessibility tools". But I
> don't introduce any a11y support tools...
> 
> And I found the bug 1163004 which is always enables a11y feature on windows
> 10.
> So does the combinations of bug 1198459 and bug 1163004 cause always to
> disable e10s on Windows 10?
> 
> 
> I'm sorry if this assumption is incorrect.

This only affects devices with touch input displays.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.