cc @rakudrama.
Added Area-Library, Library-Html, Triaged labels.

This comment was originally written by stefan.s...@gmail.com

Additional information: Step 2 of the tutorial works in Firefox. A name appears in the badge as soon as you type.

First step with the reported problem: Step 3.

This comment was originally written by cogman...@gmail.com

Should be noted this issue appears in Firefox 31 beta, The code appears to work in Firefox 30 and Firefox Aurora (32)

Oops, I filed a bug too. 19509.

Issue #19509 has been merged into this issue.

This comment was originally written by stefan.s...@gmail.com

Reported to Mozilla as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1027011

Be aware: It isn't a Mozilla bug if the difference between Firefox 30/32 to Firefox 31 is within the standard. It's just reported and no cause of the error is determined yet.

I looked a little bit into it.

in FF30 the getNativeInterceptor succeeds whereas in FF31 it fails.

in FF30:
proto == objectProto == EventPrototype

in FF31:
proto == UIEventPrototype
objectProto == InputEventPrototype

the tag is "InputEvent".

I hope this helps Stephen (or someone else in Seattle) to fix the issue.

cc @blois.

This comment was originally written by ope...@mozilla.com

Any news on this one? Firefox 31, which implements InputEvent (defined in W3C DOM 3 Events) will be released in 3.5 weeks

I looked into it. The issue is upstream. We're generating our bindings from Blink IDL, the current version of which doesn't seem to have InputEvent. Dart sometimes lags behind latest Blink, but I just checked Chrome Canary (Version 38.0.2071.0) and no dice there, either (strange!).

Presumably Chrome/Blink is implementing this soon? I did a quick web search but couldn't find any tracking bugs. Jacob, do you know who could fill us in on the Blink status of this?

cc @jacob314.

This comment was originally written by @sethladd

Can we assign a milestone? Do you think this will be fixed in 1.6?

Sigh, had typed a much longer comment but got lost due to simultaneous update :(

@sethladd -- yes, this is critical and should be fixed in 1.6. Not only that, if it affects already compiled apps (https://code.google.com/p/dart/issues/detail?id=13285) we have to backport it to 1.5 stable and get the word out to recompile affected apps...

@efortuna -- I think the fix is in native_helper.dart. There's getTagFirefox in there, but I don't think we should put it there since this is a new standard Event: http://www.w3.org/TR/DOM-Level-3-Events/ not a browser specific API. Instead we should add a generic hook similar to _fixDocumentHooksTransformer (I think ... the code has changed completely since I last looked).

Added this to the 1.6 milestone.
Removed Priority-Unassigned label.
Added Priority-Critical label.

p.s. thank you Stefan for pinging this bug! (https://news.ycombinator.com/item?id=7956827)

This comment was originally written by ope...@mozilla.com

"We're generating our bindings from Blink IDL, the current version of which doesn't seem to have InputEvent. Dart sometimes lags behind latest Blink, but I just checked Chrome Canary (Version 38.0.2071.0) and no dice there, either (strange!). "

What is strange with that? Blink is behind other browsers in many event handling
related cases.

This comment was originally written by bzb...@mit.edu

In general, Blink's IDL doesn't match the spec IDL in many cases. So if you generate bindings based on Blink's IDL and expect them to work in other browsers, you will definitely run into problems.

No, the Blink IDL is our starting point of API generation, but we make adjustments to run for other browsers. I'll make the change in native_helper.dart. CL will be out shortly.

Fix put in at r37838!

Set owner to @efortuna.
Added Fixed label.

Marked this as blocking #20148.