Firefox:Configurable Keybindings: Difference between revisions

(Please remember Help, which needs to display keyboard shortcuts!)
Line 47: Line 47:


I would personally say distribute by default, on by default, removeable via advanced options, most people would love its use, (I assume), and have a need for it, though would have no clue to look at UMO to use it, and with the proposal here should be simple enough for your average user to use without ruining much of their set-up at all...so on by default, removeable in the same vein that DOMi is addable. [[User:Callek|Justin Wood (Callek)]] 02:35, 3 Jan 2005 (PST)
I would personally say distribute by default, on by default, removeable via advanced options, most people would love its use, (I assume), and have a need for it, though would have no clue to look at UMO to use it, and with the proposal here should be simple enough for your average user to use without ruining much of their set-up at all...so on by default, removeable in the same vein that DOMi is addable. [[User:Callek|Justin Wood (Callek)]] 02:35, 3 Jan 2005 (PST)
=== Comments [[User:Waldo|Waldo]] ===


'''Please''' remember that the keybindings that are set need to be shown correctly in Help documentation!  If the user can edit everything willy-nilly, having a static Help document that only reflects the shipping keyboard shortcuts is going to be very nearly useless. --[[User:Waldo|Waldo]] 02:32, 13 Jan 2005 (PST)
'''Please''' remember that the keybindings that are set need to be shown correctly in Help documentation!  If the user can edit everything willy-nilly, having a static Help document that only reflects the shipping keyboard shortcuts is going to be very nearly useless. --[[User:Waldo|Waldo]] 02:32, 13 Jan 2005 (PST)
=== Comments [[User:Joewalp|Joe Walp]] ===
Implementing this reliably is nontrivial because keybinding is controlled via:
* platform bindings
* event handlers attached to the wrapped DOMWindow object by the loaded page w/ capture
* event handlers attached to parents of the focused element on the loaded page
* handler entities defined via XBL
* event handlers attached via XBL [rare]
* event handlers attached to the window object w/ capture
* XUL event handlers attached to parents of the focused element
* XUL key entities
In some cases it's not obvious what precedence these bindings should have.  And I expect that some application-level behavior that ought to be configurable is currently implemented as XBL handler entities.  Changing this could be tricky.
Managing key entities is complicated by a bug.  If you remove a key entity then invoke the previously bound action, it causes a crash (ref: Firefox 1.5).
For the StumbleUpon extension, I opted to use event handlers attached to the window object w/ capture.  Feel free to contact me if you're interested in the justification for that.<br>
-- [[User:Joewalp|Joe Walp]] 05:01, 24 September 2006 (PDT)
12

edits