Changes between Version 2 and Version 3 of Ticket #698


Ignore:
Timestamp:
May 28, 2016, 2:16:34 PM (8 years ago)
Author:
elexis
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #698 – Description

    v2 v3  
    33 * Pressing enter when a button has focus should cause an onPress event
    44
    5  * Tab switching of focus between controls - the ordering could be the same as in the page XML, left to right for children of a given parent object, and/or support a "taborder" property to override the defaults. Obviously not every control should be included in the tabbing, restricting to input controls seems reasonable.
     5 * Tab switching of focus between controls (-> #3235) - the ordering could be the same as in the page XML, left to right for children of a given parent object, and/or support a "taborder" property to override the defaults. Obviously not every control should be included in the tabbing, restricting to input controls seems reasonable.
    66
    77 * Support keyboard accelerators, which are usually specified with an ampersand (&) character in the caption of an input control (the corresponding accelerator is often underlined). This way a dialog that asks "&Yes"/"&No" could be answered with the Y or N keys.
    88
    99 * Keys could be useful for navigating text lists and dropdowns. Imagine a map list with hundreds of items and you want to skip to "Punjab 1", it should be possible by tapping `P` to jump to maps named starting with 'p'. That's the simple case; a more complicated extension would be typing multiple characters to match partial words, but that gets messy and is never fully intuitive.
     10
     11 -> Implemented for dropdowns but not ordered lists