3 ms·
OT: Just in case webdevs reads this: you might want to markup clickable things as clickable (<a>). If you need a datapoint: I'm using Vimium for Chrome.
by chelmertz 10y ago
OT: Just in case webdevs reads this: you might want to markup clickable things as clickable (<a>). If you need a datapoint: I'm using Vimium for Chrome.
- slazaro 10y agoAlso, I think there should be an option to show all of the websites. I don't want to keep clicking to see which websites I use, I just want to browse by scrolling.
- smholloway 10y agoDoes something like https://twofactorauth.org/data.json https://twofactorauth.org/data.json satisfy? It's not the most usable interface, but it should have all the data.
- smholloway 10y agoHmmm, what are you seeing that's not clickable? I don't use vimium and I can click on the site name, docs links, and tell-them-to-two-factor-via-twitter. Whoop. Looks like the tiling system is relying on JavaScript instead of <a> tags for links: ``` <div id="communication" class="category column" style="display: block;"> <h5 class="ui icon header"> <i class="circular chat icon"></i> <small>Communication</small> </h5> </div> ``` The contributors are pretty responsive, so I'd recommend noting the issue: https://github.com/2factorauth/twofactorauth/issues https://github.com/2factorauth/twofactorauth/issues
- Moeancurly 10y agoI agree with your sentiment, but a minor nitpick: [Stop using anchors as buttons!][1] An anchor would be good here if the clicking the icons also triggered a URL change, but as it stands a button would be semantically most appropriate [1]: (http://blogs.ancestry.com/techroots/buttons-vs-anchors/ http://blogs.ancestry.com/techroots/buttons-vs-anchors/)