If XULElement key has got keycode="VK_F3", then it event "command" doesn't handle




Keyboard: Navigation
13 years ago
9 years ago


(Reporter: Gaydukova Svetlana, Unassigned)


Windows 2000

Firefox Tracking Flags

(Not tracked)



(1 attachment)

921 bytes, application/vnd.mozilla.xul+xml


13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217

<?xml version="1.0"?>
<?xml-stylesheet href="chrome://global/skin/" type="text/css"?>
<window id="example-window" title="Example 6.3.2"
  <key id="paste-key" keycode="VK_F2"
          oncommand="alert('Paste invoked')"/>
  <key id="paste-key2" keycode="VK_F3"
          oncommand="alert('Paste invoked 2')"/>
<menubar id="sample-menubar">
  <menu id="edit-menu" label="Edit" accesskey="e">
    <menupopup id="edit-popup">
      <menuitem id="paste-command" accesskey="p" key="paste-key" label="Paste"
                   oncommand="alert('Paste invoked')"/>
      <menuitem id="paste-command2" accesskey="a" key="paste-key2" label="Paste2"
                   oncommand="alert('Paste invoked 2')"/>

The code on keypress VK_F2 should alert('Paste invoked') and it does this.
Also on keypress VK_F3 it should alert('Paste invoked 2'), but it doesn't do this. 

Reproducible: Always

Steps to Reproduce:
1.open xul file in Mozilla
2.press VK_F3

Actual Results:  
Nothing happen

Expected Results:  
should appear alert('Paste invoked 2')

Comment 1

13 years ago
Created attachment 183344 [details]
test file

try press VK_F2, VK_F3 and see reaction

Comment 2

13 years ago
wfm Mozilla/5.0 (Windows; U; Win98; de-DE; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
wfm Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b2) Gecko/20050511

alerts are seen only if JS is enabled.

Comment 3

13 years ago
Works for me
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050513

If it works for anyone else, please comment (or simply resolve the bug)
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

13 years ago
confirm Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20050909

Comment 6

12 years ago
Running on Thunderbird 1.0 codebase, I encountered this problem. Looking into it, I tracked down to mozilla/content/xbl/src/nsxblwindowhandler.cpp, line 251.  In nsXBLWindowHandler::WalkHandlersInternal, there is a point here handling the event is contingent upon the a call to EventMatched(currHandler, aEventType, aEvent); This call never returns true for the F3 key.

I followed this call to nsxblprototypehandler.h line 88.  Here the two nsCOMPtr's are compared, and no two are ever found to match.  

This section of the codebase is outside of my area of expertise, but I thought it might help someone else find a starting point.
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
QA Contact: bugzilla → keyboard.navigation
You need to log in before you can comment on or make changes to this bug.