Added Area-HTML, Triaged labels.

This comment was originally written by antonm@google.com

This is by design: we don't allow cross-frame DOM access. Please, use isolates or postMessage to communicate.

Added WontFix label.

This comment was originally written by antonm@google.com

cc @vsmenon.

This comment was originally written by oking...@google.com

Given this, what is the desired method for decorating an existing page? (One which is external to the dart application - think chrome extension style)

Please see 20146 - we're rethinking this limitation.

Currently, you have two options:

• js interop
• place the decorating dart code on the target page and use postMessage to communicate to it (may not work for your example)

  ---

  Added Duplicate label.
  Marked as being merged into [next] Dart should allow cross frame dom access to windows from the same origin. #20146.

This comment was originally written by oking...@google.com

Thanks for fast response, I'll follow that issue.

Option 2 isn't a good option in this case. I really wish the dart APIs were cross-frame here because the js interop is painful :/

postMessage has TERRIBLE restrictions,

@DanielJoyce Usually it helps to provide concrete use cases where a bug or missing feature blocks you. I'm not entirely sure for this issue though. Looks a bit like a dead horse. But there where quite a few other issues which were finally fixed with nice solutions after a long time.

Which might be true. But TypedScript is stealing darts thunder, and with the death of Google Dev Editor, so dies the biggest pressing need for Google to fix the issues inherent in trying to write multi-screen chrome apps.