Make scripts support Chrome.

[derekriemer]

Hi:
User scripts supported are in chrome. However, https://www.chromium.org/developers/design-documents/user-scripts seems to claim we need //@match in the //userScript part.

[derekriemer]

The @include is supported, but it's actually breaking for me. Something's not working, and I haven't tried yet to see what, because chrome dev tools a11y is dodgey.

[derekriemer]

The default user scripts stuff doesn't seem to work either. You get a "I can't install scripts like this from here, maaaaaaaahahahahaahahaha" dialog.

[derekriemer]

More info. https://www.chromium.org/developers/design-documents/user-scripts

[derekriemer]

I'm seeing rumors on the web that Chrome won't let you install extensions not from the store period.Even with developer mode on I can't seem to. so much for user scripts.

[derekriemer]

Well, okay, even with @include, I can confirm that it works with tamper monkey! Here's a little bit of hacky work around. The TL DR boils down to it is impossible toClick open on a file and get the script to install if you're working on the actual script. This is a bit unfortunate, but there's a workaround. Just paste the URL to the script on your local system with file:// before the actual file path. Then it whenever you need to refresh the script, say if you're actually working on editing the script in chrome, you simply press alt D, and then hit enter. Clicking on a link to a script will work and install it with TamperMonkey.

…

On Mon, Mar 13, 2017 at 7:39 AM, Derek Riemer ***@***.***> wrote: I'm seeing rumors on the web that Chrome won't let you install extensions not from the store period.Even with developer mode on I can't seem to. so much for user scripts. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFGivWlh4FihHpU2EVMCkJTFVx7ez_ukks5rlUcZgaJpZM4MbOkT> .

-- Derek Riemer: Improving the world one byte at a time! - University of Colorado Boulder Department of computer science, 4th year undergraduate student. - Accessibility enthusiast. - Proud user of the NVDA screen reader. - Open source enthusiast. - Skier. Personal website <http://derekriemer.com>

[jcsteh]

As discussed with @derekriemer elsewhere, the actual issue in Chrome is that the tweaks to make certain GitHub tables accessible don't work in Chrome. This is because Chrome's support for role="table" is broken. I'll file a bug against Chrome.

[jcsteh]

Filed Chrome issue regarding role="table": https://bugs.chromium.org/p/chromium/issues/detail?id=730928

I updated the readme in 8525246 to mention Tampermonkey for Chrome. Also, I did some work on the Slack and GitHub scripts related to Chrome. There are probably other things that need to be fixed for Chrome that I haven't seen yet, but let's address those as they arise.