> Anyway, can Safari pass
> http://www.w3.org/WAI/UA/TS/html401/cp0101/0101-ACCESSKEY-BUTTON.html#test1
> or select entry "F" on
> http://www.w3.org/WAI/GL/tests/accesskey3.html
Safari 4 for Windows can pass the accesskey test, and it can select
entry "F" in that list *as long as the focus is on t
Owen Leonard wrote:
> [I asked... please keep attributions]
> > Why would accesskeys conflict with built-in browser shortcuts?
>
> I simply mean that we can't choose from the full array of possible
> keys because some keys will already be mapped to default browser
> functions. For instance, in Saf
> > not all keys or key combinations
>> will be available (for instance, because of conflicts with built-in
>> browser shortcuts).
>
> Why would accesskeys conflict with built-in browser shortcuts?
I simply mean that we can't choose from the full array of possible
keys because some keys will alrea
Owen Leonard wrote:
> The advantage of the accesskey method is of course that it's not
> javascript-dependent. The disadvantage is that different browsers
> handle accesskeys differently, a combination of keys is usually
> required (Alt+ or Ctrl+Alt+), and not all keys or key combinations
> will b
Hi,
On Tue, Jul 14, 2009 at 3:35 PM, Owen Leonard wrote:
> Currently the core set of accesskeys are "u" for Check Out, "r" for
> Check In, and "q" for Search. The javascript-based match for these is
> "Alt-u," "Alt-r," and "Alt-q." Darrell Ulm just submitted a patch that
> would add "F12" to the l
It seems like you are also talking about two different types of
shortcut keys, global keys and context keys. For example the current
accesskeys are global. No matter where you are in koha, they work.
The new functionality for F12 looks like it only works in circulation.
There's no reason F12 co
