Great satire but let's create that same for combobox with server side filtering. Now you have problem because it's not possible with native HTML elements. Many re-implementations are result of missing native elements.

▲

chuckadams 2 hours ago | parent | next [-]

Anything doing server-side work is going to have to be at least somewhat custom. The main problem is there isn't a standard "combobox" at all to speak of: we're still mostly stuck with the same carved-in-stone widget set from Mosaic, whereas native toolkits were more inventive even in the late 80s. Where's Athena's 2d panner widget, for example?

I didn't read any satire in the article at all, it just laid out all the built-in behaviors that a proper button has, and how much work it is to reimplement all of them. Something declarative and CSS-like would have been ideal for customizing elements, but instead we got the half-assed Custom Elements API and the completely different DX atrocity that is Web Components.

I can't really fault Custom Elements too much though, it's an imperfect API for an imperfect DOM and it's better than waiting forever for perfection. But I don't extend the same generosity to the Web Components spec.

	▲	ezekiel68 22 minutes ago \| parent [-]
		I imagine the commenter was referring to the article title wrt satire.

▲

an hour ago | parent | prev | next [-]

[deleted]

▲

repeekad 3 hours ago | parent | prev | next [-]

Correct me if I’m wrong, but my understanding is Google would love to make more web standards native (including selectors which have improved on chrome but are basically broken on safari) but Apple holds back progress in a (borderline?) anticompetitive way

	▲	thyristan an hour ago \| parent \| next [-]
		I'm not sure if it's Google's fault alone. My impression is, all browsers are holding back on everything HTML-native and JavaScript-free. There have been literal decades of no progress, and only tiny steps forward as of late. We've had things like https://doc.qt.io/qt-6/qtwidgets-module.html since the late last millenium. Back in the day, there was Delphi, now there is Lazarus, with even nicer Data-Bound widgets. Look at some tutorial for those, that's like magic, and also from before 2000! Does anyone know why there have been 3 lost decades in native HTML widgets? Any ideas how to fix this?
	▲	troupo 8 minutes ago \| parent \| prev \| next [-]
		Not Google. Microsoft, of all companies started this project: https://open-ui.org/ when Google was busy breaking the web web components, hardware APis etc. Google was very, very, very late to the project and of course immediately trampled all over it like they did with all the web standards. Apple isn't holding back progress on that. They are all in on it, though they do tend to be more cautious than the "break fast and lose things" Google.
	▲	chuckadams 3 hours ago \| parent \| prev [-]
		Because Google is known for holding back in order to not get too far ahead of other browsers?

▲

daniela-scott 3 hours ago | parent | prev | next [-]

Right, and the article kind of proves your point even a plain button needs formAssociated + ElementInternals to feel native. A combobox with server-side filtering is a whole other galaxy.

▲

youngtaff an hour ago | parent | prev [-]

<input> with <datalist> can provide a combobox

Missing part is dynamically updating the datalist in an efficient way

	▲	roundabout-host 11 minutes ago \| parent [-]
		[dead]