ePUB and ProQuest Ebook Central
Report ID: 1503473978
When a user on a Chromium-based browser has the Zotero connector extension enabled, ePUB titles on the ProQuest Ebook Central Platform do not display content. Example: https://ebookcentral.proquest.com/lib/vcu/reader.action?docID=31339340&ppg=1
https://s3.amazonaws.com/zotero.org/images/forums/u14904473/y2ghe163ul2ops074fos.png
As soon as the connector is disabled, the content loads without issue.
https://s3.amazonaws.com/zotero.org/images/forums/u14904473/tuco5nvs95ylbac6jcgu.png
This issue can be recreated on Mac and PC, on Chrome, Brave, Edge. Issue does not appear on Safari or Firefox Browsers.
PDF-based titles on this platform do not encounter this issue and load normally
When a user on a Chromium-based browser has the Zotero connector extension enabled, ePUB titles on the ProQuest Ebook Central Platform do not display content. Example: https://ebookcentral.proquest.com/lib/vcu/reader.action?docID=31339340&ppg=1
https://s3.amazonaws.com/zotero.org/images/forums/u14904473/y2ghe163ul2ops074fos.png
As soon as the connector is disabled, the content loads without issue.
https://s3.amazonaws.com/zotero.org/images/forums/u14904473/tuco5nvs95ylbac6jcgu.png
This issue can be recreated on Mac and PC, on Chrome, Brave, Edge. Issue does not appear on Safari or Firefox Browsers.
PDF-based titles on this platform do not encounter this issue and load normally
1 refers to the extension restarting, then the other is:
Uncaught (in promise) SecurityError: Failed to read a named property 'document' from 'Window': Blocked a frame with origin "https://ebookcentral.proquest.com" from accessing a cross-origin frame.
I contacted Proquest about it and they said to just disable the extension if I want to see full-text for EPUB. Modifying the site data permissions for the extension also works.
I work for a university library and this is going to be confusing to explain to users. Is there a fix in the works? Is this something Zotero needs to fix, or Proquest?
Thanks!
(We recently had to make some changes for Chrome's updated extension framework, and the changes ended up conflicting with the behavior of a few sites. We've now switched to a different approach that should avoid problems like this. Thanks for reporting.)
It works! Thank you!
-Sarah