Back

@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.

if “nobody cares” is there a chance of people who do care fixing it?
@phryk @alcinnz

@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

Fork!

(99% sad joking. 1% the growing feeling that we’re going to have to have alternate browsers anyway, so…)

Maybe as the EU develops its own standards.

@phryk @alcinnz

@clew @phryk I'd be interesting in seeing (simpler) specs which describe the state of Lynx, NetSurf, Dillo, WeasyPrint, my own work, etc...

Setting up a good governance process would be the trick!