Updates:
Status: Started
Owner: [email protected]
Comment #1 on issue 24867 by [email protected]: Add support
for "experimental" extension APIs
http://code.google.com/p/chromium/issues/detail?id=24867
There are two ways that I think implement this quickly and correctly.
1) Create a set of top level modules names (eg. chrome.history) which are
linked to
the module "experimental" in the extension_process_bindindgs.cc method
GetPermissionName. This allows all module implementation, tests, and
experimental
extras to require minimal changes when the API is approved. API approval
simple
requires the addition of the module name to the permissions enumeration and
out of
the mapping to "experimental."
2) Modify the bindings so that from the extension_api.json file one can
define
modules in the chrome.experimental namespace. All callbacks, functions,
etc must be
prefixed with chrome.extension before their module. This insures that
author are
aware of their experimental state, but makes the transition for
experimental to
approved messy.
In CL 313001 I have implemented #2. But from an API developer's
perspective I would
prefer #1.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
