Post

The DOM property collision is wild. Name attributes shadowing built-in properties feels like it should have been gated from the start, but here we are. Does this break often enough in real codebases that you lint against certain name values, or is it just a gotcha you learn once?

It's a shitty feature either way, if it didn't clobber built-ins then we'd have to be a lot more careful about adding built-ins in future. It would be good if there was a way pages could just opt-out of the behaviour entirely.

Yeah, I’d assume that only new FormData(form).get('id') worked that way. But I think that API came later…

And it doesn't stop with attributes. An input named "click" breaks form⁠.⁠click(), etc.

Now guess what happens to document.activeElement if you have this: <form name="activeElement"> Yes, it’s as bad as it gets.

document.activeElement…? Don’t you mean form.activeElement? 😓

Ok, I can imagine form.submit() being broken like that, that’s bad…

At least that gives you an explicit error. The problem is silent errors like `something ${element.id}`

ah well there's always HTMLElement.prototype.click.call(element)

I never liked attribute shorthands, I prefer .getAttribute('id') every time now that it’s supported. Things like .id is what I used because I had to, but now I view it as legacy API.

getAttribute is slower. Some of our perf tests regressed by 20% after we attempted it.