Accessibility/Electrolysis2: Difference between revisions

tweek
(added aes list)
(tweek)
 
Line 1: Line 1:
== tl;dr Status ==
== tl;dr Status ==
* Looks like we need to cache a11y child data in the main process.
* 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
** 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


Confirmed users
1,085

edits