Broken for players served over HTTPS (e.g. Google Music)

[max99x]

On Chrome 36 (Linux, but probably doesn't matter), KeySocket is broken by new security limitations:

[blocked] The page at 'https://play.google.com/music/listen?u=1#/all' was loaded over HTTPS, but ran insecure content from 'ws://localhost:1337/': this content should also be loaded over HTTPS.

It's possible that just changing the scheme to "wss" will solve this, but I don't know if all of the server implementations which KeySocket uses automatically support secure connections.

[hobeone]

Chrome 35 introduced support for global hotkeys. This plus the Google
Music chrome extension removes the need for keysocket for Google music.
Can you see if that works for you?

On Thu, May 29, 2014 at 11:48 AM, Max Shawabkeh notifications@github.com
wrote:

On Chrome 36 (Linux, but probably doesn't matter), KeySocket is broken by
new security limitations:

[blocked] The page at 'https://play.google.com/music/listen?u=1#/all' was
loaded over HTTPS, but ran insecure content from 'ws://localhost:1337/':
this content should also be loaded over HTTPS.

It's possible that just changing the scheme to "wss" will solve this, but
I don't know if all of the server implementations which KeySocket uses
automatically support secure connections.

—
Reply to this email directly or view it on GitHub
#59.

Daniel Hobe hobe@gmail.com

[max99x]

Are you referring to this extension? Unfortunately that doesn't seem to work for me. Are there any Chrome flags that need to be toggled?

[hobeone]

Yeah, that extension. Once you have it installed kill any keysocket daemon
that you already have running. Then check out chrome://extensions/. At
the bottom of the page there's a link for keyboard shortcuts. You should
see entries for the Google Play Music extension. Make sure the drop down
for the keys is set to "Global". Reload your google music tab and see if
you can control things now.

On Thu, May 29, 2014 at 12:20 PM, Max Shawabkeh notifications@github.com
wrote:

Are you referring to this extension
https://chrome.google.com/webstore/detail/google-play-music/icppfcnhkcmnfdhfhphakoifcfokfdhg?hl=en?
Unfortunately that doesn't seem to work for me. Are there any Chrome flags
that need to be toggled?

—
Reply to this email directly or view it on GitHub
#59 (comment).

Daniel Hobe hobe@gmail.com

[max99x]

Google Play Music does not appear in the Keyboard Shortcuts list (other extension do appear), and neither does it show up in the extensions list. It does appear on the Apps page though.

That app is also marked as being last updated on August 6, 2013, long before Chrome 35 was out.

[hobeone]

Did you set it up as described here:

http://www.omgchrome.com/browser-uploading-now-available-google-music/
http://www.omgchrome.com/keyboard-control-scope-chrome-extensions/

On Thu, May 29, 2014 at 1:38 PM, Max Shawabkeh notifications@github.com
wrote:

Google Play Music does not appear in the Keyboard Shortcuts list (other
extension do appear), and neither does it show up in the extensions list.
It does appear on the Apps page though.

That app is also marked as being last updated on August 6, 2013, long
before Chrome 35 was out.

—
Reply to this email directly or view it on GitHub
#59 (comment).

Daniel Hobe hobe@gmail.com

[max99x]

Hmm, I don't have that option in Labs. Perhaps it's not available on Linux or only enabled for a sample of users.

[tsbertalan]

This worked for me. Had to enable Google Play's shortcuts as global, and also actually set the shortcuts to the media keys.

[wernight]

Thanks @hobeone for this tip. I think it's actually better if it's natively supported. The option is pretty hidden but I have it on Chrome 36 on Linux.

[camalot]

Not that it is a keysocket issue directly, but chrome itself seems to have issues with the native key support and the logitech G510 on Windows 8.1 Update 1. I have the keyboard at work (Windows 7) and at Home (Windows 8.1U1). The native keyboard hook stuff works on Windows 7, does not work in Windows 8.1U1.

[linef4ult]

^ Im using a G510 on Win7 64 Pro and its not working :/

[borismus]

HTTPs doesn't have anything to do with this. Closing