![]() about: or view-source:) where it doesn't work at all, or doesn't work consistently so one must disable it. 99% of the time it works perfectly, but then there are the handful of sites or browser specific pages (eg. I've tried tridacyl and other vim-style plugins for browsers several times in the past, but always end up uninstalling them in disappointment, because it's not possible to have a consistent experience. I can't build muscle memory or be confident using a feature if it only works 90% of the time. I've found that a feature or shortcut is only useful if it's consistent. Your comment on '"Ctrl+F" instead as I'm too scared to try "/" now' really resonated with me, because I've thought about this before. My point was going to be that consistency is key. ![]() the 'modern' web is pain.Īnyway, this wasn't going to be a rant. ![]() It's not just overridng default shortcuts, but custom context/rightclick menus, custom 'links' (where clicking them runs javascript code to window.open, instead of being a real link), custom form fields that advertise 'excellent accessibility', where the fields would have been accessible anyway if they didn't decide to reimplement them, disabling text selection, overriding focus styles because the accessible styles 'look ugly'. So many sites seem to feel the need to reimplement things that are already part of most browsers or even in the spec. ![]() Unfortunately this is broken on the "modern" web as many web pages "helpfully" override the "/" keyĪrgh this kind of thing makes me really cross. ![]()
0 Comments
Leave a Reply. |