Node.parentElement should be Element | null, not HTMLElement | null

[trusktr]

Hello! I'm new to this. How exactly would I change that?

For example, a <g> element somewhere inside an <svg> element will have a .parentElement that is an SVGElement, which is not an HTMLElement.

[saschanaz]

This is true and was done by #885, but then reverted by #970. Seems there were tons of breakages. @orta

I doubt we can do this if that was the case, but it at least needs some comment about it.

[trusktr]

I left some comments. Plus imagine when something useful like this comes out in the future:

WICG/webcomponents#942

The only proper type for these DOM APIs is Element.

[HolgerJeromin]

@trusktr
Technically you are right in moving to Element. But this would break many applications. Most do only deal with HTML and would need manual adjustments.
Developers should be happy and not annoyed by forcing them to touch all DOM touching code with compiled for years.
SVG users are right now forced to type assert anyway.

ref microsoft/TypeScript#42067 (comment)
microsoft/TypeScript#4689 (comment)

[orta]

Yeah, this has been well covered and discussed. I don't think I've seen anything new in the comments to warrant keeping this issue around. If you'd like you, can fork this repo to ship your own dom.d.ts build with this in 4.5, but it's unlikely to come in by default given the trade-offs.