Re: Electrolysis and Accessibility
Re: Electrolysis and Accessibility I am frustrated with IE. It has been sluggish and unresponsive for the majority of the time that I have been using it. I tried FireFox but my screen-reader is %50 responsive.Is this new addon improving FireFox? URL: http://forum.audiogames.net/viewtopic.php?pid=263627#p263627 ___ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Electrolysis and Accessibility
Electrolysis and Accessibility Firefox will introduce Electrolysis starting with version 48 for a small fraction (1%) of users, for about 50% of users in version 49, and more later. The 50% or so aren't running add-ons or screen readers. This is an eligibility requirement for Electrolysis.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 itself communicated from subprocesses. Of course, this creates scheduling complications, so while processes are now more isolated, they are nevertheless blocked from operating asynchronously with respect to the main process. Google have solved this problem in Chrome using DOM caches in the main process, which eats up more memory but guarantees that the main process can't get hung up on subprocesses as often.A 64-bit multi-process architecture is a big rea son I recommend Chrome. Maybe we poor, helpless blind can finally get off IE or Safari with a browser that's not made by Google. URL: http://forum.audiogames.net/viewtopic.php?pid=263489#p263489 ___ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
Electrolysis and Accessibility
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. URL: http://forum.audiogames.net/viewtopic.php?pid=263489#p263489 ___ Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
