The current name is needlessly verbose, inconsistent, and doesn't match the style guide.
Lets hope that dart:html will be able to export dart:dom's XmlHttpRequest simply by typedef.
This isn't a class that can be exported by typedef as we want to use XMLHttpRequest.on.load instead of XMLHttpRequest.addEventListener
Removed Area-UI label.
Added Area-DOM label.
Set owner to @vsmenon.
Added this to the M1 milestone.
Removed Area-DOM label.
Added Area-HTML label.
Issue #3133 has been merged into this issue.
Removed Priority-Medium label.
Added Priority-High label.
Set owner to @efortuna.
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
@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 ...
This is a good opportunity to document HttpRequest. When we change the name, the MDN docs will be even less relevant.
This comment was originally written by branflake...@gmail.com
Would ResourceRequest name be a better fit?
This was committed in r11070.
Added Fixed label.