AnitaTang / js-hotkeys

Automatically exported from code.google.com/p/js-hotkeys
0 stars 0 forks source link

key events not bubbling up to the application level in safari #15

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. create a simple jQuery.Hotkeys enabled page with a single handler for 'n'
2. hit the 'n' key to fire the action
3. hit command-n intending to create a new browser window

What is the expected output? What do you see instead? even with 
{propagate:true}, the 
command-n key event is gobbled by the page and never passed back up to the 
browser. this 
makes pages which use jQuery.Hotkeys rather frustrating for users as their key 
commands 
appear to stop working.

What version of the product are you using? On what operating system?
safari 3.1.1 / Mac OS X 10.5.3

Please provide any additional information below.
this must be possible since the key navigation on http://ffffound.com/ uses say 
the h key yet 
command-h is still fed to the browser.

Original issue reported on code.google.com by jeanpie...@gmail.com on 21 Apr 2008 at 7:42

GoogleCodeExporter commented 8 years ago
lightbox2 also offers navigation via keyboard which seems to bubble up to the 
browser. when viewing an image 
set, one can use the 'n' key to go to the previous image and 'p' the previous, 
but one can still hit command-n to 
create a new window.
  http://www.lokeshdhakar.com/projects/lightbox2/
appears to be using prototype/scriptaculous, ffffound.com uses prototype as 
well.

Original comment by jeanpie...@gmail.com on 23 Apr 2008 at 12:24

GoogleCodeExporter commented 8 years ago
the test page http://jshotkeys.googlepages.com/test-static.html works as 
expected
with my mac/safari
osx: 10.5.2
safari: 3.1.1

Is it the same by you?

Original comment by Afro.Sys...@gmail.com on 23 Apr 2008 at 3:53

GoogleCodeExporter commented 8 years ago
well it works as expected meaning that the proper keys are being displayed as 
pressed - but my concern lies 
with the inability to bubble keys up to the browser. if i open the test page 
you linked to, click in the page to 
give it key focus and hit command-n to open a new window, a new window is not 
created, the page displays 
that 'n' was pressed and eats event - this is expected since the 
{propagate:true} option is not being used. 
unfortunately, even when it is used, key events are not bubbled up.

even more so, jquery-hotkeys is a bit over bearing - if i create a key event on 
the 'n', it still gets triggered for 
any key combo making use of the 'n' key, not just 'n' alone as i would expect.

the note from the wiki about page acknowledges the issue no?

Note
Firefox is the most liberal one in the manner of letting you capture all 
short-cuts even those that are built-in 
in the browser such as Ctrl-t for new tab, or Ctrl-a for selecting all text. 
You can always bubble them up to 
the browser by using option propgate:true.

Others, (IE) either let you handle built-in short cuts, but will add their 
functionality after your code has 
executed. Or (Opera/Safari) will not pass those events to the DOM at all.

So, if you add Ctrl-Q or Alt-F4 and your Safari/Opera window is closed don't be 
surprised.

Original comment by jeanpie...@gmail.com on 23 Apr 2008 at 4:35

GoogleCodeExporter commented 8 years ago
Did you experience this symptom only with the Command key. Since the current 
version
is not supporting the command (mac) button, it treats Command+n as if only 'n' 
was
pressed. Yet, I believe the this issue will be solved in the coming days. As 
far as I
can tell, I didn't have any other problem on mac+safari combination.
BTW: this will be the same with FF and perhaps Opera on mac.

Original comment by Afro.Sys...@gmail.com on 8 Sep 2008 at 5:06

GoogleCodeExporter commented 8 years ago
see here:
http://code.google.com/p/js-hotkeys/issues/detail?id=26

Original comment by Afro.Sys...@gmail.com on 8 Sep 2008 at 5:24

GoogleCodeExporter commented 8 years ago

Original comment by Afro.Sys...@gmail.com on 21 Sep 2008 at 5:37

GoogleCodeExporter commented 8 years ago
I've started having this problem in the last day or two with any google 
pages... ie: Whenever I am on any kind of 
google page - mail, calendar, blooger, even this page right here - my command 
key is rendered useless. Does 
anyone know if Google have changed anything and is anyone else experiencing 
this problem? REALLY 
frustrating...

Got a 17" MacBook Prop with 10.5.5 and using Safari 3.1.2...

Original comment by adrian.w...@gmail.com on 10 Nov 2008 at 7:17

GoogleCodeExporter commented 8 years ago
the problem you describe has nothing to do with this module. see, 
google-calendar or
gmail or blogger or any other page you have mentioned are not part of this
jQuery-Plugin anyhow.

Original comment by Afro.Sys...@gmail.com on 10 Nov 2008 at 8:30