Object and Embed elements are JS functions in Firefox and Chrome 47, so dart2js does not find interceptors for them

[alan-knight]

Same root cause as #23466 but more general.
@rakudrama

[alan-knight]

Note: tests that fail because of this are marked Pass, RuntimeError while we have some bots on 46 and others on 47. This should be fixed once they're all updated.

[alan-knight]

All the bots are on 47 now and the tests are properly marked RuntimeError.

[mit-mit]

@alan-knight what else remains here? I noted the bug is not assigned to anyone.

[whesse]

This high priority bug should be assigned to someone on the dart2js html library team, or it shouldn't be high priority.

[alan-knight]

The high priority original problem now has a workaround, so we can probably remove this from high priority.

[mit-mit]

Moving to 1.15

[denisoby]

@alan-knight could you give the link or example of this workaround?

[alan-knight]

As I remember, the issue was setting some content through Angular, so it was going through setting innerHtml, which meant that it was getting touched by Dart code, although it didn't need to be. So there are a few possible workarounds. One is don't use that element :-). Another is that if it's in static HTML and you're not programmatically manipulating it through Dart it shouldn't be a problem. I think that even if you go through setting innerHtml/appendHtml/etc, if it's HTML that you control and you can use NodeTreeSanitizer.trusted, then that should work. And I guess the last-ditch workaround is write a fragment of JS to do the work you need to do on that element and invoke it from Dart.

[DisDis]

possible duplicate #25785 ?

[alan-knight]

Yes, I think that's the same underlying issue.

[mit-mit]

Clearing out 1.15 milestone as the last full push to dev has happened. If any changes are required before 1.15 is shipped, please file a merge request