search

lovasoa / dezoomify-extension

A browser extension to detect zoomable images in web pages and downloading them with dezoomify
https://lovasoa.github.io/dezoomify-extension/
GNU General Public License v3.0
48 stars 2 forks source link

failure to find URLs from a different subdomain in chrome #12

Closed lovasoa closed 3 years ago

lovasoa commented 4 years ago

Initially reported by @rhythmus in https://github.com/lovasoa/dezoomify/issues/428#issuecomment-699672522

Hi @lovasoa, thanks for the quick follow-up! I had success, using:

However, on Chrome it seems to keep failing. I previously tried unsuccessfully always using the browser extension for Chrome. I now tried again in Chrome, but on a newer machine:

While the Dezoomify browser extension is listening and I am scrolling/zooming the OpenSeadragon viewer, and image tiles are being loaded and drawn onto a \<canvas> in BritishMuseum.org webpages, the extension fails to find the TileSource URLs. Or perhaps it does, but anyway does not show the badge telling that it did. Also note that the extensions seems to consume lots of CPU on Chrome. My fans blow heavily and Chrome’s Task Manager shows a resource intensive process — until I deactivate the Dezoomify extension. Thought you might want to know.

Anyhow, I’m happy to be now able to use Dezoomify on BritishMuseum.org, at least on my old machine, using Firefox. Thanks, and keep up the good work!

lovasoa commented 4 years ago

Webpage: https://www.britishmuseum.org/collection/object/P_F-4-171

lovasoa commented 4 years ago

Thanks @rhythmus for reporting this. I'll try to reproduce and investigate the issue when I get the time.

lovasoa commented 4 years ago

I can't reproduce the high resource usage, but I can reproduce the extension not finding the image. I think this is due to the image being hosted on a different subdomain (media.britishmuseum.org), and chrome not giving the extension access to the subdomain when it was activated on the main domain.

I created a different issue for the high resource usage.

lovasoa commented 3 years ago

The next version of the extension we'll request the permission to listen on all requests, and thus fix this issue.