(Archived) [BUG] Chrome web clipper treats SHIFT key as TAB or "," key

[roschler 158]

I am using Chrome version 14.0.835.202m on Windows XP SP3 32-bit. When entering tags into the tag edit box the Evernote web clipper provides, hitting the SHIFT key causes the currently highlighted (selected) auto-complete suggestion to be filled in. This makes entering tags with shifted characters a problem. You have to first make sure you hit the BACKSPACE key to wipe out the auto-fill suggestion before you type the shifted key. It appears to treat the SHIFT key like the comma "key" or TAB key, thinking you are accepting the auto-fill suggestion.

-- roschler

[jefito 5,588]

I didn't see quite that behavior. What I saw was the Shift key (also the Alt key and Ctrl key, for that matter) dismissing the dropdown tag list, but not finishing the auto-selection: the highlight for the unmatched portion remains, and you can keep typing, and the dropdown will come back, or type a comma to clear the highlight and accept, or Tab key to accept and move to the comment field, or Enter to accept and clip. In short, it's not the same as Tab or comma.

[roschler 158]

I didn't see quite that behavior. What I saw was the Shift key (also the Alt key and Ctrl key, for that matter) dismissing the dropdown tag list, but not finishing the auto-selection: the highlight for the unmatched portion remains, and you can keep typing, and the dropdown will come back, or type a comma to clear the highlight and accept, or Tab key to accept and move to the comment field, or Enter to accept and clip. In short, it's not the same as Tab or comma.

Yes that's correct, when you are typing the very first tag. But after you type a comma and start typing the second tag, you get the problematic behavior I reported. At least that's what is happening to me. I just tried it on this forum page. After pressing the Evernote clipper button, in the Tag edit box:

I typed "dog" 
Then a comma to close the tag
Then q&a to add "q&a" as a second tag

As soon as I typed "q" I got the auto-fill suggestion "qserrequests" at the cursor location highlighted in blue (selected). When I typed an ampersand (SHIFT + 7) "qserrequests" was automatically filled in followed by the ampersand I typed, so I ended up with "qserrequests&" as my second tag and the cursor positioned after the ampersand at the end of the line.

-- roschler

[jefito 5,588]

I think that you need to type a space character after you type a comma for the auto-matching to turn on again.

[roschler 158]

I do type a space character after I type a comma. Just didn't mention it since it's a reflex. I tested again to make absolutely sure and the bug is still there.

-- roschler.

[jefito 5,588]

Interesting. That's not what i'm seeing, also retested. BTW: Chrome 14.0.835.202 m

[Owyn 457]

Could not reproduce in XP/Chrome.

Just starting careful retest.

[roschler 158]

Thanks for testing Owyn. I see it every time. Seeing as jefito has the same Chrome version, this is looking very strange.

@jefito - are you running on a Windows box or a Mac?

@Owyn - I assume you are still on your Linux box running Windows in a VM?

-- roschler

[Owyn 457]

Chrome: 14.0.835.202m

OS: Windows XP SP3 32-bit (VirtuallBox VM)

Test affect of various tag deliminators.

ad ->adblock = first in dropdown list

ad -> nothing = duplicate tag

adv -> Advertising = first in dropdown list

ad,-> ad = new tag, explicit delimator

ad -> no-op (still have dropdown)

adO -> adobe (explicit test of shift-o)

[jefito 5,588]

I am running on Win 7, both at home and at work (tested both machines).

[Owyn 457]

@Robert

Can you retest this with the new beta Chrome Clipper?

I tested it with tags which started with caps and it worked fine for me, but, you were getting different results before.