When you used a built-in interactive HTML UI component (e.g. textarea, select, checkbox) in the browser was it because? A) Accessibility?
B) A better polished/integrated user experience than any JS library provides. C) Meh I just needed to throw something together.
-
Show this thread
-
This is the biggest differentiator between something like the Web and React Native. The focused investment in polished native UI components by far that of web browser and JS libraries combined. The web has only optimized scrolling finite content (unless you use scrollbars).
4 replies 2 retweets 13 likesShow this thread -
Replying to @sebmarkbage
I'm not buying this argument. Can you unpack it more, especially as it relates to people who are developing content for the web?
1 reply 0 retweets 1 like -
Replying to @wycats
The quality of primitives on the web is poor. E.g. contextual menus, stack navigation, buttons, video controls, infinite scrolling lists with context, date pickers etc. This was known before the mobile era. Many reimplementations of <select /> and jQuery UI solved a real problem.
4 replies 2 retweets 15 likes -
Replying to @sebmarkbage
Every reimplementation of <select> on the web since the beginning of time that I have come into contact with has made my experience worse. It got even worse on mobile. Flex was not an improvement.
2 replies 0 retweets 10 likes -
Replying to @wycats
Fair but native <select> is also terrible. If we built web with only native components we'd never get a decent experience. That's my point. We shouldn't necessarily rely on people reimplementing. The browsers could do it but they have to try harder.
1 reply 0 retweets 5 likes -
Replying to @sebmarkbage @wycats
The status quo is that both browsers and JS ecosystem are doing a poor job. The JS ecosystem often has an excuse because we don't have access to the primitives that are needed. That's not to say that it would be good even if we did. The game theory might not align.
2 replies 0 retweets 6 likes
There's, I think, very little chance we could do it well in JS because it would involve having JS access to primitives that, if designed well, would be tantamount to designing a good control. Maybe they'd magically design good primitives but the past few years are not promising.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.