Recent searches
Search options
One of my main #web gripes: HTML forms can only use GET and POST methods.
If <form> also supported PUT and DELETE, you could easily map CRUD to HTTP methods and that would feel so much cleaner than splitting functionality for the same types over a bunch of different paths.
@phryk I don't understand why forms can't use PUT or DELETE, speaking as a browser-dev...
@alcinnz Well, it's my old nemesis again – JS.
JS *can* use any HTTP method, so the W3C simply doesn't care.
I think it's for the same reason that the W3C doesn't care about <details> open/close not supporting CSS transitions – "just use JS".
Honestly, bare HTML has been feeling abandoned for *well* over a decade.
Like, the last change I actually noticed was them deprecating <keygen>, which at the time even Berners-Lee protested.
@clew Well, you'd have to convince the HTML working group at W3C.
A long, long time ago, I tried engaging in constructive criticism with W3 groups, but from my experience, it's not gonna happen.
If you have a couple hundred hours to burn to essentially add two lines to the spec, you might have a shot, but sadly this is nowhere near as simple as just handing in a PR and bringing a solid argument as to why it should be merged… :/
// @alcinnz
@clew Yeah, the web has been a big mess ever since it started being used as application delivery mechanism.
What I myself would greatly prefer would be a subset of the current web that doesn't support JS/wasm, but just HTTP, HTML, CSS and SVG.
That enables a lot while sidestepping most of the problems the web currently has and would bring us closer to the big web of hyperlinked pages that the web was initially envisioned as.
And if you extend HTTP/HTML with partial page updates (IIRC this was planned at some point, but later dropped) you can do almost everything JS is currently used for – with the only remainder being things that should either be native applications or UX stuff that should be implemented in the base spec.
Our project is a public browser!
Our project is a public browser and efficient HTML standard!
Our project is a pb, eHs, and a governance model that can’t be captured by embrace-extend-extinguish!… I’ll come in again.
(Seems like an amplifying-feedback group of things, though, even though they’re all so hard to start.)