On Mon, Dec 4, 2017 at 8:58 AM, Axel Hecht <l...@mozilla.com> wrote: > Am 04.12.17 um 05:42 schrieb Jet Villegas: > >> >> On Sun, Dec 3, 2017 at 05:15 Axel Hecht <l...@mozilla.com <mailto: >> l...@mozilla.com>> wrote: >> >> Am 01.12.17 um 16:45 schrieb Justin Wood: >> > Hey Everyone, >> >> [snip]
I hope we can change that (testing on localized builds) with this proposed >> change. We’ve gotten reports that localized builds (and related usage; >> e.g., input method editors) cause A11y API activation, which triggers other >> bugs for us. >> > > My gut reaction is "that shouldn't happen", though, well, no idea what > IMEs do. Do we have bugs tracking these? I'd love to be on CC on those. > It can happen. IMEs often have prediction features and they need to examine the context under which the input is happening. One example we recently learned of is a Japanese IME feature ATOK's "insight" which analyzes focused web content for input prediction and switching dictionaries. The main side effect is performance. We need to do two things here: 1. Add more caching to our Windows e10s a11y solution. 2. Do something smart about the different kinds of clients that instantiate a11y. This will likely be two things: blocking 'a11y' clients who that are just being ridiculous, and better, copying what Chrome does and instantiate only 'portions' of our a11y support... think of this as having a 'lightweight' mode, although it may be that we have multiple levers. Cheers, D _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
