getting error as "TypeError: chrome.mediaGalleries.removeAllGalleryWatch is not a function" in chrome 51
Reported by
sairavis...@gmail.com,
Jun 7 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36 Steps to reproduce the problem: Use any chrome extension which is using removeAllGalleryWatch method of chrome.mediaGalleries, you will see this error. What is the expected behavior? What went wrong? you will see this error in 51 version chrome only, in 50 no error. Did this work before? Yes 50 version before update to 51 version Chrome version: 51.0.2704.84 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 21.0 r0
,
Jun 9 2016
@Sai: Looks to have been removed due to low usage: https://chromium.googlesource.com/chromium/src/+/804c8718a55a41c3b783337f78ef0caf2368cf4c
,
Jun 9 2016
Thanks x31forest! I've contacted one of our writers to see if we can update the docs and avoid future confusion.
,
Jun 10 2016
What would be a good automated practice for dev teams to detect such breaking changes? I would have liked to detected this issue at the moment it was marked as deprecated.
,
Jun 10 2016
A surprise deprecation can be unpleasant. Those who implement the deprecation can manually add in a console warning (as in the case with Geolocation API on unsecure origins) and update the docs before landing. I’m not sure what an automated solution would look like, but it could save everyone time. If you have ideas, please do make a feature request.
,
Jun 10 2016
Hey - Yeah sorry about that. It's odd that the updated docs haven't made it to https://developer.chrome.com/apps/mediaGalleries yet. Yes, next time a console warning would be a good idea. I recommend using chrome.mediaGalleries.removeGalleryWatch instead. The app will need to keep track of the gallery watch IDs and loop over them. |
|||
►
Sign in to add a comment |
|||
Comment 1 by l...@chromium.org
, Jun 9 2016