on-change event triggered twice

[gaplyk]

http://jsbin.com/bodelite/1/edit

After input value changed we receive 2 events CustomEvent and Event "change". Is this is an issue or it should behave like this?

[ebidel]

According to the Shadow DOM spec, the change event is supposed to stop at the root of the node tree.

core-input accounts for this by firing a CustomEvent for change: https://github.com/Polymer/core-input/blob/master/core-input.html#L331:L334

However, what I'm seeing from native SD is the the original change is actually bubbling up: http://jsbin.com/zimatace/1/edit. Is that expected?

Assigning to @sorvell for clarification.

[frankiefu]

Yes, this is a bug in native SD: https://code.google.com/p/chromium/issues/detail?id=398527&thanks=398527&ts=1406661473

[gaplyk]

here is full example:

http://jsbin.com/bodelite/4/edit

[tjsavage]

Good catch! Closing here since it's a native SD bug, looking to be fixed in the spec.