Zotero Connector for Chrome does not work properly
Hi, I have found that the Zotero connector for Chrome does not work properly for a Ruby on Rails site if that site uses Turbo Drive (https://turbo.hotwired.dev/handbook/drive) for navigation. The connector for Firefox works fine.
To reproduce the problem:
1. Open https://katalog.ub.uni-paderborn.de/cdi/s?sr[q,title]=Operating System Noise in the Linux Kernel in Chrome.
2. Click on the title "Operating System Noise in the Linux Kernel" to open the details page for that title. The "click" triggers a Turbo Drive navigation (not a full page reload).
3. On that details page is a DOI that should be picked up by the Zotero connector. The connector icon should change to a folder icon, but it is still the empty "document" icon (Save to Zotero (Webpage with snapshot)). If you reload the page the folder icon appears.
Doing this in Firefox works as expected.
Since I'm the developer of this site, I tried to fix this by dispatching the ZoteroItemUpdated event as mentioned here (https://www.zotero.org/support/dev/exposing_metadata#force_zotero_to_refresh_metadata
) in the event of a Turbo Drive navigation. But that doesn't solve the issue. Is there something else I can try?
Thanks
To reproduce the problem:
1. Open https://katalog.ub.uni-paderborn.de/cdi/s?sr[q,title]=Operating System Noise in the Linux Kernel in Chrome.
2. Click on the title "Operating System Noise in the Linux Kernel" to open the details page for that title. The "click" triggers a Turbo Drive navigation (not a full page reload).
3. On that details page is a DOI that should be picked up by the Zotero connector. The connector icon should change to a folder icon, but it is still the empty "document" icon (Save to Zotero (Webpage with snapshot)). If you reload the page the folder icon appears.
Doing this in Firefox works as expected.
Since I'm the developer of this site, I tried to fix this by dispatching the ZoteroItemUpdated event as mentioned here (https://www.zotero.org/support/dev/exposing_metadata#force_zotero_to_refresh_metadata
) in the event of a Turbo Drive navigation. But that doesn't solve the issue. Is there something else I can try?
Thanks
Thanks
We actually fixed this but had to roll back the changes due to breakage.