Closed Bug 556752 Opened 16 years ago Closed 15 years ago

Add-on Builder generates add-on which eat all key events

Categories

(addons.mozilla.org Graveyard :: Developer Pages, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED
5.12.9

People

(Reporter: bugzilla, Assigned: jorgev)

Details

Attachments

(1 file)

Current Add-on Builder https://addons.mozilla.org/en-US/developers/tools/builder will generate ff-overlay.xul which includes: <keyset id="mainKeyset"> <key id="key_openSidebar_{name}" command="viewSidebar_{name}" /> </keyset> This key element eat all key events and beginner developers cannot notice about it, cannot find how to fix it. Instead, generate code like this: <!-- set key attribute and change modifiers to enable accesskey -- see: https://developer.mozilla.org/en/XUL/key --> <keyset id="mainKeyset"> <key key="" modifiers="accel" id="key_openSidebar_{name}" command="viewSidebar_{name}" /> </keyset>
Cesar, Jorge, thoughts?
Looks like the bug report is correct. Furthermore, I don't think the Add-on Builder should generate shortcut keys, given how difficult it is to get them right and not conflict with anything else.
Jorge, would you be willing to write a patch for fizzypop to fix this? We still have a good amount of add-ons built using the packager. http://svn.mozilla.org/projects/fizzypop/trunk/
Assignee: nobody → jorge
Target Milestone: --- → Q4 2010
I need to know who reviews this code. This patch removes the shortcut key code entirely. It looks like fixing it would take a lot of work, and either way we shouldn't be encouraging the use of shortcut keys.
mfinkle and cesar are responsible for fizzypop I think.
Comment on attachment 486462 [details] [diff] [review] Patch V1. Axe all the shortcut key code from the overlay template Looks OK to me. We don't seem to use <key> anywhere else in the extension templates.
Attachment #486462 - Flags: review+
Fixed, r76510.
Status: NEW → RESOLVED
Closed: 15 years ago
Priority: -- → P3
Resolution: --- → FIXED
Target Milestone: Q4 2010 → 5.12.2
Turns out that I didn't commit to the right repo :/ (bug 556754 comment #12) Reopening to get this right.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Target Milestone: 5.12.2 → 5.12.7
Target Milestone: 5.12.7 → 5.12.9
Committing again on r82041.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
Verified fixed.
Status: RESOLVED → VERIFIED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: