←back to thread

367 points lemonberry | 1 comments | | HN request time: 0s | source
Show context
macawfish ◴[] No.24641169[source]
I recently stumbled across "shoelace", which at a glance seems like an example of what the article is hoping for. It's a thoughtfully designed library of UI web components.

https://shoelace.style/

replies(3): >>24641310 #>>24641427 #>>24642064 #
dheera ◴[] No.24641310[source]
... and it suffers from the same oversight every other web component library (polymer, mdl) suffers from:

- I can't swipe left/right between the tabs

- I can't pull the menu out from the left by swiping the entire page right

Two of the most basic touch navigation metaphors aren't supported. To be fair, Polymer and MDL don't support the above either. But this is why HTML5 apps are still not up to par with native apps. I really want to see a web component library with full touch functionality -- tab swiping, pinch zoom on images, pull to refresh on lists and card lists.

https://shoelace.style/components/tab-panel

replies(3): >>24641433 #>>24641512 #>>24645921 #
1. schwartzworld ◴[] No.24641512[source]
I could see arguments for keeping that sort of behavior out of a base library. I've never had to implement a menu that swipes out like that, but I could see it being a complex behavior to get right.

if you need that use case, it seems easy enough to implement