Cleanup method signatures that were incorrect due to a lack of understanding about how Dart generic…

Cleanup method signatures that were incorrect due to a lack of understanding about how Dart generics work.

BUG=
R=alanknight@google.com, terry@google.com

Committed: https://code.google.com/p/dart/source/detail?r=43562

[Jacob, 2015-02-06 02:58:28]

jacobr@google.com changed reviewers:
+ alanknight@google.com, terry@google.com

[Jacob, 2015-02-06 02:58:29]

Without this fix querySelectorAll acts more like it is returning List<dynamic>
than List<Element> which causes the analyzer to not provide any useful auto
complete on the Element class if you write
document.querySelectorAll("div").last
document.querySelectorAll("div")[0]
etc

[terry, 2015-02-06 16:15:40]

On 2015/02/06 02:58:29, Jacob wrote:
> Without this fix querySelectorAll acts more like it is returning List<dynamic>
> than List<Element> which causes the analyzer to not provide any useful auto
> complete on the Element class if you write
> document.querySelectorAll("div").last
> document.querySelectorAll("div")[0]
> etc

Is this a breaking change?

[Jacob, 2015-02-06 16:20:59]

On 2015/02/06 16:15:40, terry wrote:
> On 2015/02/06 02:58:29, Jacob wrote:
> > Without this fix querySelectorAll acts more like it is returning
List<dynamic>
> > than List<Element> which causes the analyzer to not provide any useful auto
> > complete on the Element class if you write
> > document.querySelectorAll("div").last
> > document.querySelectorAll("div")[0]
> > etc
> 
> Is this a breaking change?

It is not a breaking change. The underlying object was always an
ElementList<Element> not the nonsense type ElementList<dynamic>
All thtat was broken was the analyzer giving the user sensible autocomplete
messages.

[terry, 2015-02-06 17:14:50]

lgtm

[Alan Knight, 2015-02-06 18:00:49]

lgtm

[Jacob, 2015-02-06 19:16:40]

Committed patchset #1 (id:1) manually as 43562 (presubmit successful).