Hello All,
I''ve run across something that looks like a bug and wanted to throw
it out there for anyone else''s input before I submit a bug report and
patch. This is only observed in Safari 2.0.3 with Mac OS X 10.4.5 - I
haven''t tried any other versions of Safari.
I''ve got 2 fields:
text input 1
text input 2 with autocomplete
If you:
1. Enter some value in field 1
2. Enter a value in field 2
3. Allow the autocomplete to finish and select a value
4. Then shift-tab back to field one
then the observer event is set to run with the timeout which kicks
off the startIndicator().
It seems that this is because Safari sends a 0 for the shift-tab
keyCode, rather than a 9 which you would expect. I was able to fix it
in my local copy of controls.js by simply adding another check for
Safari and keyCode of 0 in addition to the existing checks for
KEY_TAB and KEY_RETURN.
Has anyone else seen this? It''s probably worth a bug report for
Safari too if this is really what''s going on.
Thanks,
Matt
