Chrome Extension Team: Breaking Change to captureVisibleTab - intended change or bug?

[VisiboTech]

Starting Chrome 12+ (tested with 12.0.742.60) we discover that calls
to captureVisibleTab on any urls without any explicit requested
permission in the manifest will fail. Is this intended? This runs
completely different to behavior in previous versions (no permissions
other than Tabs were required) and should be considered a breaking
change. Many extensions (including some widely-used, featured
extensions, including ours) rely on this to work, be it capture a
screenshot, or show a tab preview, so please do notify us developers
to act accordingly if it is not a bug. Can any one from Google can
verify/confirm/clarify this issue?

[Boris Smus]

This is indeed a known issue. Thanks for reminding us! Kathy just updated the docs to reflect the changes.

http://code.google.com/chrome/extensions/whats_new.html

http://code.google.com/chrome/extensions/tabs.html#method-captureVisibleTab

Thanks,

- Boris

--
You received this message because you are subscribed to the Google Groups "Chromium-extensions" group.
To post to this group, send email to chromium-...@chromium.org.
To unsubscribe from this group, send email to chromium-extens...@chromium.org.
For more options, visit this group at http://groups.google.com/a/chromium.org/group/chromium-extensions/?hl=en.