search

jasonzhyan / google-axs-chrome

Automatically exported from code.google.com/p/google-axs-chrome
0 stars 0 forks source link

ChromeVis default key config breaks text input in content-editable divs #5

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Press Shift+S/A/W/Q/C/X/P/O while trying to type in a content-editable div 
(which is quite common if you ever want to capitalize the first letter of a 
sentence with a word that begins with any of those letters)

What is the expected output? What do you see instead?
Expected either better default shortcuts that don't interfere with common text 
input, or for the key events to be ignored when a content-editable div is being 
used.

Additionally, it should especially ignore these key binds when ChromeVis isn't 
even being used.  I know it makes an effort to ignore the keys when a form 
field has focus.  It should be able to detect when the current caret/selection 
is a child node of a content-editable element.

What version of the product are you using? On what operating system?
ChromeVis 2.4.4.  It may cause this on other pages, but the particular page 
where it came to my attention was Google Wave / Wave in a Box.  It occurs with 
both of them.

Please provide any additional information below.

Original issue reported on code.google.com by crac...@gmail.com on 15 May 2011 at 5:15

GoogleCodeExporter commented 8 years ago 
I'm encountering this bug frequently in Google+, specifically when typing new 
posts or comments. Had to disable ChromeVis to make G+ usable. I know this is 
essentially a "Me too" post, but it will be a pretty big example of it the wild 
soon.

Original comment by aisi...@gmail.com on 7 Jul 2011 at 2:53

GoogleCodeExporter commented 8 years ago

Original comment by rshea...@google.com on 28 Sep 2011 at 6:45

GoogleCodeExporter commented 8 years ago 
Apologies in advance for the "me too" comment. It's been so long since there's 
been an update to this extension that I'm curious if it's still being 
developed? I like everything about ChromeVis except the fact that I keep having 
to turn it off due to the issue listed above. I haven't found a replacement  
that works as well and as simply. I would really appreciate a fix, even if it 
meant I had to pay for the updated extension.

Original comment by mj00...@gmail.com on 17 Jul 2012 at 10:08