Stop suppressing generation of bindings with Promise.

Stop suppressing generation of bindings with Promise. Add some tests for DOM APIs that answer promises.

R=vsm@google.com

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

[rmacnak, 2014-09-25 22:59:55]

rmacnak@google.com changed reviewers:
+ terry@google.com, vsm@google.com

[rmacnak, 2014-09-25 22:59:56]

I see an error running go.sh about duplicate definitions. Any idea why?

https://codereview.chromium.org/605853003/diff/1/tools/dom/scripts/htmldartge...
File tools/dom/scripts/htmldartgenerator.py (right):

https://codereview.chromium.org/605853003/diff/1/tools/dom/scripts/htmldartge...
tools/dom/scripts/htmldartgenerator.py:217: return
This blocks an error about duplicate definitions

[rmacnak, 2014-09-30 06:53:12]

rmacnak@google.com changed reviewers:
+ leafp@google.com

[terry, 2014-09-30 15:01:56]

https://chromiumcodereview.appspot.com/605853003/diff/60001/tools/dom/scripts...
File tools/dom/scripts/htmldartgenerator.py (right):

https://chromiumcodereview.appspot.com/605853003/diff/60001/tools/dom/scripts...
tools/dom/scripts/htmldartgenerator.py:217: return
Ryan,

The problem is that there are now a bunch of overload methods that need private
members those methods need to be added to the list private_html_members in 
htmlrenamer.py.  I'll send the changes in htmlrenamer.py

[terry, 2014-09-30 15:30:54]

https://chromiumcodereview.appspot.com/605853003/diff/60001/tools/dom/scripts...
File tools/dom/scripts/htmldartgenerator.py (right):

https://chromiumcodereview.appspot.com/605853003/diff/60001/tools/dom/scripts...
tools/dom/scripts/htmldartgenerator.py:217: return
On 2014/09/30 15:01:55, terry wrote:
> Ryan,
> 
> The problem is that there are now a bunch of overload methods that need
private
> members those methods need to be added to the list private_html_members in 
> htmlrenamer.py.  I'll send the changes in htmlrenamer.py

And you'll need to add the method to an darttemplate for each interface to
delegate to the hidden method (_methodname).  I can help you with that.

[vsm, 2014-09-30 18:22:27]

lgtm once terry's comment is resolved

https://chromiumcodereview.appspot.com/605853003/diff/60001/tests/html/fontfa...
File tests/html/fontface_loaded_test.dart (right):

https://chromiumcodereview.appspot.com/605853003/diff/60001/tests/html/fontfa...
tests/html/fontface_loaded_test.dart:42: expect(fontFace.load(), throws);
Test that the future completes?

[rmacnak, 2014-10-02 01:32:13]

I'm thinking it makes more sense to forward the overloaded ones in a later CL
where they can be tested. Right now this CL enables just to enough to test the
basic promise plumbing is working.

https://chromiumcodereview.appspot.com/605853003/diff/60001/tests/html/fontfa...
File tests/html/fontface_loaded_test.dart (right):

https://chromiumcodereview.appspot.com/605853003/diff/60001/tests/html/fontfa...
tests/html/fontface_loaded_test.dart:42: expect(fontFace.load(), throws);
On 2014/09/30 18:22:26, vsm wrote:
> Test that the future completes?

This tests that the future completes with an error (the url for the font points
to nothing).

[vsm, 2014-10-15 22:27:10]

lgtm

[rmacnak, 2014-10-16 01:17:53]

Committed patchset #8 (id:140001) manually as 41136 (presubmit successful).