New cross platform shortcut keys

Currently we use the ACCESSKEY attribute to create shortcut hotkeys on the “open next” and related buttons visible when you are viewing feeds. The problem is that the keys used to select an ACCESSKEY vary by platform and browser. This means that we have to sniff for different browsers and platforms to show you the correct key combinations.

Now that Firefox will be switching in 2.0 from Alt + key to Shift + Alt + key, ACCESSKEY is officially dead to me.

We’re switching to javascript shortcut keys that will be the same on all platforms. Some of the current keys we’re using like “z” will cause shortcut collisions on some platforms, so the keys will have to change.

Here’s what I’m thinking:
Open Next: CTRL + ,
Mark Read: CTRL + .
Mark Read and Open Next: CTRL + /
Add Feed: CTRL + \

Let me know if you think these combinations are comfortable and if they cause any collisions for you.

Unfortunately, the javascript shortcut keys won’t work in Opera (if anyone knows of a way let me know), though any Opera user that was actually pressing Shift + Esc then the accesskey probably died of fatal carpal tunnel long ago.

3 Responses to “New cross platform shortcut keys”

  1. Aleksandersen Says:
    October 15th, 2006 at 7:09 am

    Hi,

    Why just don’t use * accesskey=”H” rel=”home”>Home/*>?

    Then it would be Web browser dependant which keys that would be used, but it would work with all browsers on all systems.

  2. zoo33 Says:
    October 20th, 2006 at 5:28 am

    Let me just warn you that the combinations ctrl + / and ctrl + \ may not work that good on international keyboards. On my Swedish mac keyboard / is accessed through shift + 7 and \ through shift + alt + 7. Keyboard shortcuts like cmd + \ (which becomes cmd + alt + shift + 7) usually don’t work.

  3. me Says:
    October 26th, 2006 at 3:04 pm

    First, I love newshutch.com and would marry you if it becomes legal in NJ ;)

    Second, please give back my shortcut keys. I cant, really cant, live without them. I will have to either overdose or move back to FireFox 1.5…