Why does Chrome not yet work with orca on GNU/Linux? It now supports Firefox fairly well now. Is the Linux code base behind Windows?
*Don Marang*Vinux Software Development Coordinator - vinuxproject.org <http://www.vinuxproject.org/> There is just so much stuff in the world that, to me, is devoid of any real substance, value, and content that I just try to make sure that I am working on things that matter.
-- Dean Kamen On 6/6/2011 3:26 AM, Varun Khosla wrote:
DOM of Chrome and Firefox is based On single technology called Gecko developed by Mozilla. This means that Chrome should have started working with Jaws much earlier and such delay simply signifies plane laziness. The gecko technology is the only reason why The same scripts being used in both browsers. 5/29/11, Sina Bahram<sbahram@xxxxxxxxx> wrote:Sorry for the cross posting, but as this fundamentally affects, or at least can, how most of us interact with the web, I thought I'd share. I fired up the latest Google chrome, as I do from time to time, to play around with it, and I noticed that jaws 12 started reading me the page. First I thought, oh cute, the virtual cursor recognition finally got smart enough to recognize the chrome window as non-static text, but then I said, hmm, that's reading awfully well, so I hit h and navigated by header, and I went to different URLs, and they all read correctly. Further investigation shows that jaws is aliasing chrome to Firefox. The Firefox scripts, in fact, are what is loaded if you do an insert+q. So, apparently no longer is NVDA the only windows screen reader that supports chrome. Good to see, I thought. Btw, I checked, and sure enough, the line: chrome=Firefox appears in the default confignames.ini shipping with jaws. Would have been nice to know ... just a thought. Take care, Sina __________ View the list's information and change your settings at //www.freelists.org/list/programmingblind
