Accessibility/Electrolysis2

From MozillaWiki
Jump to navigation Jump to search

tl;dr Status

  • Linux/Mac: remote calls from main process and cache as needed.
  • Windows: AKlotz will bend COM to his will.
    • Original plan was to proxy (to content process) all calls coming in to the main process from desktop os, sync if necessary (Desktop a11y API is sync), and then tune for performance which we expected would mean caching child accessibility data in the main process where necessary, but on Windows we hit reentrancy snarls like: bug 1219350. Putting a11y into its own process not viable: bug 1222255 - RESOLVED INVALID

aes+ Triaged Blockers (Windows)

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Work to Implement Accessibility for Sandboxed E10s

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


Mitigation Work (while accessibility work unfinished)

Bugzilla query error

Array ( [type] => error [message] => http-bad-status [params] => Array ( [0] => 429 [1] => Unknown Error ) ) 1


TODO: add remaining orphan bugs to tracking bug