Rename "XMLHttpRequest" -> "HttpRequest" in dart:html

[munificent]

The current name is needlessly verbose, inconsistent, and doesn't match the style guide.

[rakudrama]

Lets hope that dart:html will be able to export dart:dom's XmlHttpRequest simply by typedef.

[jacob314]

This isn't a class that can be exported by typedef as we want to use XMLHttpRequest.on.load instead of XMLHttpRequest.addEventListener

[vsmenon]

Removed Area-UI label.
Added Area-DOM label.

[vsmenon]

Set owner to @vsmenon.
Added this to the M1 milestone.

[iposva-google]

Removed Area-DOM label.
Added Area-HTML label.

[vsmenon]

Issue #3133 has been merged into this issue.

[vsmenon]

Removed Priority-Medium label.
Added Priority-High label.

[vsmenon]

Set owner to @efortuna.

[sethladd]

XMLHttpRequest is a mainstay name for web developers. I don't support changing the name unless we significantly enhance the interface, make is Darty, and unify it with dart:io's HttpRequest. If we do so, we must heavily document that XMLHttpRequest is now HttpRequest (so the inevitable searches will still work)

See also issue #2677

[jmesserly]

@seth: yeah, we're going to do that--make it Darty and unify with dart:io :). We need to get dart:html types to be as nice as jQuery APIs (e.g. jQuery.ajax)

Totally agree on needing some way to help people find the new names. I find this issue with lots of the DOM apis. one idea is to "typedef" the old names and make them @­deprecated pointing at the new names. Basically some other way to tell the editor to help users when they try to use "XMLHttpRequest", "HTMLElement", or "appendChild" etc ...

[sethladd]

This is a good opportunity to document HttpRequest. When we change the name, the MDN docs will be even less relevant.

[DartBot]

This comment was originally written by [email protected]

---

Would ResourceRequest name be a better fit?

[efortuna]

This was committed in r11070.

---

Added Fixed label.