4 ms·
I keep getting burned by chrome's automatic updates. They have twice killed xmltree extension I use and I have to wait for the extension owner to update it.
by iamjustlooking 16y ago
I keep getting burned by chrome's automatic updates. They have twice killed xmltree extension I use and I have to wait for the extension owner to update it.
- abraham 16y agoAre you using the dev channel?
- cryptoz 16y agoYou can block their updates if you like (by editing your HOSTS file I imagine), but then you'd be running out-of-date software. I don't think that you can blame Chrome's updates for breaking that extension. It's much more likely that the extension is broken.
- aboodman 16y agoIn this case it was our (Chrome team's) fault. We broke an API, which we try to never do. The bug is: http://crbug.com/47726 http://crbug.com/47726. I actually thought this had already been rolled to stable, but it hasn't yet. I will check if we can get it done more quickly.
- pavs 16y agoAre you referring to this one? https://chrome.google.com/extensions/detail/gbammbheopgpmaagmckhpjbfgdfkpadb https://chrome.google.com/extensions/detail/gbammbheopgpmaag... It looks like it was updated yesterday with a bug fix.
- w1ntermute 16y agoI've never had an extension killed by an update and I run several, so I'm guessing it's that extension's fault.