4 ms·
No, but they can reimplement it in a good enough state for the vast majority of users without getting bothered by default behaviour or styling that might vary p
by Levitz 11mo ago
No, but they can reimplement it in a good enough state for the vast majority of users without getting bothered by default behaviour or styling that might vary per browser.
Which, don't get me wrong, is still a problem, accessibility matters, but if there's a reason as to why something happens, the way to fix it is to actually look at that reason.
- dpark 11mo agoA button can easily be styled and it’s definitely easier to fix the one little behavior than to reimplement all the other behaviors that are needed.
- Levitz 11mo agoAnd yet often this is not what happens. Why? People don't do stuff poorly on purpose. There's also nobody out there for which button elements are some arcane and obscure thing, we all know they exist, so what is happening? I'm not arguing for using divs instead of buttons, I'm arguing that if that happens there's a reason for it, and we ought to look at that reason and attempt to deal with it rather than admonishing developers in general.
- dpark 11mo agoDoes it happen often? The unintended behavior seems extremely discoverable. “Hey, Google. Why does my button onclick not fire correctly?” “Oh, I need to set this stupid property.” Would it be nice if this wasn’t necessary? Sure. But browsers aren’t going to break compatibility to fix this quirk. > we ought to look at that reason and attempt to deal with it I’m curious how you think we could deal with this aside from education.
- brazukadev 11mo agoIt happens often using react because react is full of foot guns