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

Problem when accessing JS context in the background page of a chrome extension #17086

Closed
DartBot opened this issue Feb 24, 2014 · 2 comments
Closed
Labels
area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report library-js

Comments

@DartBot
Copy link

DartBot commented Feb 24, 2014

This issue was originally filed by drasko.ko...@gmail.com


What steps will reproduce the problem?

  1. initialise a JsArray in a background page via context['js_list'] = new JsObject.jsify(["aaa", "bbb"]);
  2. access the JsArray in a popup page via chrome API and dart:js
    3.

What is the expected output? What do you see instead?
Expect to get a JsArray in both Dartium and dart2js scenario. Dartium works as expected, dart2js shows a JsObject instead. No known workaround.

What version of the product are you using? On what operating system?

Please provide any additional information below.
http://stackoverflow.com/questions/21976257/difference-between-dartium-and-dart2js-when-building-chrome-extensions

@sethladd
Copy link
Contributor

Added Area-Library, Library-JS, Triaged labels.

@justinfagnani
Copy link
Contributor

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

@DartBot DartBot added Type-Defect area-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. library-js closed-duplicate Closed in favor of an existing report labels Mar 7, 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-core-library SDK core library issues (core, async, ...); use area-vm or area-web for platform specific libraries. closed-duplicate Closed in favor of an existing report library-js
Projects
None yet
Development

No branches or pull requests

4 participants