Shoelace 2.0 release: UI toolkit that works with all frameworks or none at all

Re:Shoelace 2.0 release: UI toolkit that works with all fram... by DaiPlusPlus on Friday July 17, 2020 @05:46AM (#23868899)

What you’re describing are all inadequacies in current browsers to deliver a good user-experience for native HTML features. There’s no reason why browsers can’t show upload progress/status for non-AJAX uploads, and there’s no reason for browsers to keep on having poor <select> UX. etc.

JavaScript itself is a workaround - it shouldn’t be the solution.

[ Parent | on HN ]

Re:Shoelace 2.0 release: UI toolkit that works with all fram... by wruza on Friday July 17, 2020 @06:15AM (#23869030)

There's also no reason to expect browsers to become anything more than poor man's window decorations for webkit/etc, cause it didn't happen for three decades. We're on our own here and that ain't gonna change.

[ Parent | on HN ]

Re:Shoelace 2.0 release: UI toolkit that works with all fram... by gear54rus on Friday July 17, 2020 @08:58AM (#23869977)

He's describing only SOME ways to solve those use-cases. No way I'm trading extensibility and programmability of a browser for something some guy thought up to be 'ideal' solution to those cases.

[ Parent | on HN ]

Re:Shoelace 2.0 release: UI toolkit that works with all fram... by 1337shadow on Friday July 17, 2020 @06:01AM (#23868960)

If some field of the form doesn't validate then upload has to start over, unless you store the file in some tempdir and add it to the session and go through that kind of length.

What exactly do you suggest to fix select ? Even if it was parsing a JSON blob, you still have thousands of results, an autocompletion endpoint seems much more efficient.

[ Parent | on HN ]

Re:Shoelace 2.0 release: UI toolkit that works with all fram... by hfourm on Friday July 17, 2020 @07:04PM (#23877062)

Why can't we look at JavaScript as the solution instead of as the workaround

[ Parent | on HN ]