Skip to content

Documentation should mention Isolate.spawn() doesn't work with dart:html apps #17647

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

Closed
DartBot opened this issue Mar 20, 2014 · 2 comments
Closed
Labels
area-documentation Prefer using 'type-documentation' and a specific area label. closed-duplicate Closed in favor of an existing report

Comments

@DartBot
Copy link

DartBot commented Mar 20, 2014

This issue was originally filed by [email protected]


URL (if available):
https://api.dartlang.org/apidocs/channels/stable/#dart-isolate.Isolate

Issue/feedback:

    There's no mention of the fact that Isolate.spawn() doesn't work with dart:html apps.

@lrhn
Copy link
Member

lrhn commented Mar 20, 2014

Could we make Isolate.spawn work in such a way that any DOM access will throw (e.g., new StateError("concurrent access")), but the rest of the spawning will still work?

That will allow a library to use Isolate.spawn without knowing if it is in the DOM isolate, and since it doesn't know, it likely won't use the DOM anyway.

@lrhn
Copy link
Member

lrhn commented Mar 20, 2014

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

@DartBot DartBot added area-documentation Prefer using 'type-documentation' and a specific area label. Type-Defect closed-duplicate Closed in favor of an existing report labels Mar 20, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-documentation Prefer using 'type-documentation' and a specific area label. closed-duplicate Closed in favor of an existing report
Projects
None yet
Development

No branches or pull requests

2 participants