3 ms·
My guess is somebody over-engineered a "make anything into a link" helper function and then decided it was easier to just use it everywhere, rather than preferr
by munchbunny 8y ago
My guess is somebody over-engineered a "make anything into a link" helper function and then decided it was easier to just use it everywhere, rather than preferring <a> tags in the 90% of cases where it would make more sense.
How do screen readers handle these script-based links? I don't mind it from a "I have working eyes and arms" perspective, but I imagine it's kind of a pain for assisted vision?
- ljm 8y agoI think some of it is possibly just ignorance, too. For example, I've worked with a fair bit of code full of `<a onclick='...'>` tags, where the click handler basically invoked the router and redirected to a new page. Seems to happen a lot in React/JSX code.
- astura 8y agoThere is a special place in hell for whoever does this... I guess it might just bother me so much because it shows a fundamental misunderstanding of how the web works.
- komali2 8y agoI've done that before, when I was noobish and couldn't get the damn framework to work like I thought the internet worked. There was this hellish twilight area of my learning web dev where I was transitioning from how i thought the internet worked (HTML pages with anchor tags) to how it actually worked in 2015, which is slapped together framework routers that I couldn't fenangle to work with the History API.