Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

trim HTML methods to reflect restrictions on Dart-DOM APIs (e.g. iframe.contentDocument...) #1174

Closed
sigmundch opened this issue Jan 13, 2012 · 3 comments
Labels
closed-duplicate Closed in favor of an existing report

Comments

@sigmundch
Copy link
Member

Some DOM functions are different than the standard Javascript DOM API, for instance, a parent window has restricted access to the DOM of a child frame via frame.contentDocument.

We should make sure to change the HTML library in a way that makes it easy to understand/discover these restrictions (e.g. the compiler should be able to issue warnings, runtime errors are understandable).

This is strongly related with this bug: http://code.google.com/p/dart/issues/detail?id=1173

@vsmenon
Copy link
Member

vsmenon commented Apr 12, 2012

Removed Area-UI label.
Added Area-DOM label.

@dgrove
Copy link
Contributor

dgrove commented May 29, 2012

we've ripped out contentDocument. What else needs to be done here?

@vsmenon
Copy link
Member

vsmenon commented May 29, 2012

Added Duplicate label.
Marked as being merged into #2774.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

3 participants