309903 - find toolbar does not prevent pages javascript from intercepting keypresses and acting on them

Status: RESOLVED DUPLICATE of bug 276295

(Toolkit :: Find Toolbar, defect)

Description

[andy somerville]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Ubuntu package 1.0.7)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Firefox/1.0.7 (Ubuntu package 1.0.7)

if you go to a web page with java script which uses keypresses as commands and
search for something which uses a letter which has been designatged by the
javascript of that page to do something, that letter is not entered into the
find tool bar and performs the action in accordance with the java script. For an
example go to:
http://news.gmane.org/group/gmane.comp.gnome.glade.devel/last=/force_load=t
and try to use the find toolbar with any search which contains the letter 'l' or
any other letter designated in :
http://news.gmane.org/gnus.js

The find tool bar should intercept the letters and prevent javascript from
getting the event.

This often happenes as well in webmail applications which have designated
certain letters or ctrl+'letter' combinations as action keys.

Reproducible: Always

Steps to Reproduce:
1.go to http://news.gmane.org/group/gmane.comp.gnome.glade.devel/last=/force_load=t
2.type '/' for the find tool bar
3.start typing a search that contains the letter 'l'

Actual Results:  
page changes as 'l' has been designated as a hot key in javascript; letter is
not entered into the search box, and is not searched for

Expected Results:  
'l' should be entered into the find text box and considered in the search

Comment 1

[Peter van der Woude [:Peter6]]

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b5) Gecko/20050924
Firefox/1.4 ID:2005092401

WFM

Comment 2

[zug_treno]

WFM with Firefox 1.5b1 but reproducible with Mozilla 1.8b1 and SeaMonkey 1.0a,
related to/duplicate of bug 276295?

Comment 3

[andy somerville]

(In reply to comment #2)
> WFM with Firefox 1.5b1 but reproducible with Mozilla 1.8b1 and SeaMonkey 1.0a,
> related to/duplicate of bug 276295?

Upon reading bug 276295, its almost the same but importantly different. This bug
is specific to finds started with the '/' whereas the other, I believe, was the
"find" that finds links just by typing. In this case you know for certain that
the document.keypress should go to the find box and *not* to the document. In
the other case it is ambiguous

Comment 4

[:Gavin Sharp [email: [e-mail]]]

It's the same issue, fixing one will fix the other.

*** This bug has been marked as a duplicate of 276295 ***