458 karma · joined September 1, 2011
1. Google+
2. Google Duo
3. Google Hangouts
4. Google Play Games
5. Google Play Newsstand
6. Google Sheets
7. Google Assistant
Edit: Looks like .io is managed in London, and their customer service off hours match the downtime.
https://chrome.google.com/webstore/detail/morphine/fbnpehpbo...
Also open source on GitHub:
- Can't add pictures to the hall of fame after the fact.
- Can't remove pictures from the hall of fame.
- Re-uploading a ribbon picture doesn't work.
phantomjs-node: Popular but badly structured and documented. Many small ignored issues.
Then again, Closure Compiler is accepted even though the advanced mode may rewrite some of your code. And the crushers are available to everyone free of charge, so...
Once someone brought up the keyboard issue in my pull request, I researched for a while, and then made the post once I angrily realized the full extent of the problem.
If you need an example app that uses both buttons and links, here: https://chrome.google.com/webstore/detail/mghenlmbmjcpehccoa...
I know what e.preventDefault() is and when and how to use it, just simply didn't think of it when trying to find solutions. It was promptly pointed out in the G+ comments, but there are still major drawbacks to that approach.
Either way, it was well past the asking Bootstrap to add this phase by the time I wrote the post.
Of course I understand why keyboard accessibility (a benefit of href="#") is a good thing, that was a main point in the post: There's no solution for adding "buttons" (in the functionality sense) that look like standard links without major drawbacks, like a lack of keyboard control.
On a related note, I wonder how screenreaders handle buttons? I'm guessing/hope they read the labels, but if they don't...