Support for chrome.* extension APIs

[DartBot]

This issue was originally filed by imja...@gmail.com

---

With the release of Dartium, I'd love to be able to write a Chrome extension in Dart. And I currently can, as long as I don't want to take advantage of any of the Chrome-extension-specific APIs as listed on http://code.google.com/chrome/extensions/docs.html

For example, the JS chrome.browserAction.setBadgeText({text:"abc"}); would update the extension's Browser Action badge's text to "abc" -- there is no corresponding Dart code to do this.

This should be possible by wrapping the native JS, but a native Dart solution would probably be better.

[iposva-google]

Added Area-Dartium, Triaged labels.

[DartBot]

This comment was originally written by jeffbailey@google.com

---

I think triage label on this is wrong. Chrome Extension APIs are available as JavaScript APIs and are targetable by minfrog. I'd guess that these should either be a separate module, or possible be part of dart:dom.

[DartBot]

This comment was originally written by antonm@google.com

---

Removed Type-Defect label.
Added Type-Enhancement label.

[DartBot]

This comment was originally written by alexander.orlov@loxal.net

---

Actually the issue should be renamed to "Support for chrome.* extension APIs" as Chromium already supports Dart within an extension context but Dart can't access the chrome.* API yet.

[DartBot]

This comment was originally written by antonm@google.com

---

Added this to the Later milestone.

[sethladd]

Changed the title to: "Support for chrome. extension APIs".*

[vsmenon]

For now, my understanding is that we will focus on improving the existing package, which should provide all chrome APIs via JS:

http://pub.dartlang.org/packages/chrome

---

cc @dgrove.
Added AsDesigned label.

[DartBot]

This comment was originally written by benwells@chromium.org

---

I think it is more subtle than that. You can think of it as initially two parallel streams:
A. keep working on the chrome package manually using js interop
B. keep working on dart:_chrome (currently dart:chrome) autogenerated using JS

When B. is complete, cross the streams:
C. port chrome package to use dart:_chrome and expand it to cover more APIs.

I'll continue working on B.

For Dartium, the dart:_chrome wrapper would be built into Dartium itself.