But it looks like chrome.experimental.history may be "Unexperimentalified" soon.
For details see: http://code.google.com/p/chromium/issues/detail?id=32362 On Jan 15, 10:59 am, dhw <dhh...@gmail.com> wrote: > I believe as of Dev 4.0.295.0, experimental extension APIs have been > fixed to NOT work by default. See > issue:http://code.google.com/p/chromium/issues/detail?id=31537 > > You get them to work, you need to run Chrome with --enable- > experimental-extension-apis > > and the manifest.json needs: > > "permissions": [ "experimental" ] > > On Jan 15, 10:39 am, TPReal <tpr...@gmail.com> wrote: > > > > > Hello, > > > I'm on Chrome 4.0.295.0 dev and I just found out that my extension > > (TPGoogleReader,https://chrome.google.com/extensions/detail/gimgcofdoijbpkkhhlepagbdc...) > > started to fail on calls to chrome.experimental.history API. It says > > that the extension hasn't declared permission to use this API, but I > > really don't know how should I declare the permission, I mean, what is > > the string. I tried "experimental", "history" or > > "experimental.history" in the permissions section, and none of them > > worked (the extension won't load because, it says, the permission is > > incorrect). So how should I declare it correctly? > > > Also, is using experimental APIs allowed in extensions put in the > > Gallery? > > > Thanks, > > TPReal.
-- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensi...@googlegroups.com. To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
