Databases
StackOverflow2013
Postsdbo
POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
    primarykey
    data
    text
    <p>I have some code to create hotkeys for a web application. All of the hotkeys work in IE and Firefox, however <kbd>Ctrl</kbd>+<kbd>PgUp</kbd> and <kbd>Ctrl</kbd>+<kbd>PgDn</kbd> are not working in Chrome. </p> <p>After digging around for answers and writing some custom test code, I believe I have determined that this is because those events fire, in Chrome, on keyup instead of keydown. </p> <p>The default Chrome handlers for those events are firing instead of mine (or at least first) and switching the browser to the next or previous tab. If I use the hotkey to switch back to the tab with my application then my handlers catch the event.</p> <p>So my question is, is there any way to catch these events in Chrome and prevent the default functionality from running?</p> <p>The code in question is:</p> <pre><code> //These work in IE and Firefox $(this).bind('keydown', 'ctrl+pageup', (evt) =&gt; { this.prevPage(); return false; }); $(this).bind('keydown', 'ctrl+pagedown', (evt) =&gt; { this.nextPage(); return false; }); //These catch the event in chrome, but it's too late $(this).bind('keyup', 'ctrl+pageup', (evt) =&gt; { this.prevPage(); return false; }); $(this).bind('keyup', 'ctrl+pagedown', (evt) =&gt; { this.nextPage(); return false; }); </code></pre> <p>It does exactly what I want in IE and Firefox, but not Chrome. I have tried <code>evt.preventDefault()</code>, <code>evt.stopImmediatePropagation</code> and <code>evt.stopPropagation</code>. However, it does not work (I believe because my handlers are being called after the browser handlers).</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USadaaaam
    1. USJohn
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
      1. This table or related slice is empty.
      1. VTUpMod
    1. COMay be related: https://code.google.com/p/chromium/issues/detail?id=149751 (was marked as WontFix)
      singulars
      1. POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
      1. USPaul S.
    2. COI've decided to give up on this for now. The requirements were loose on what the key combination should be so I added support for ctrl+shift+pageup/pagedown for the chrome users. If anyone does have an answer though I'd love to hear it!
      singulars
      1. POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
      1. USJohn
    3. COGive us a fiddle to work with!
      singulars
      1. POPrevent default 'ctrl pageup' and 'ctrl pagedown' in Chrome
      1. USricksuggs
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload