Electrolysis and Accessibility
Firefox will introduce Electrolysis starting with version 48 for a small fraction (1%) of users, for about 50% of users in 49, and more later. The 50% or so aren't running add-ons or screen readers.
There are technical difficulties. Accessibility APIs are synchronous, and splitting Firefox up into processes means the main process will have to communicate to accessibility tools information that is communicated from subprocesses. Of course, this creates scheduling complications, so while processes are now more isolated, they are nevertheless blocked from operating asynchronously. Google have solved this problem in Chrome using DOM caches in the main process.
A 64-bit multi-process architecture is a big reason I recommend Chrome. Maybe we poor, helpless blind can finally get off IE or Safari with a browser that's not made by Google.
_______________________________________________ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
