Closed adomasven closed 2 years ago
Ok, this is actually more complicated than I suspected. I can only reproduce this when loading an unpacked Connector from a local network samba share in my existing account. I tried testing with a new chrome account with only uBlock Origin and Zotero Connector and I couldn't reproduce it whether loading Zotero Connector from the network share of installed via chrome store.
Moreover, in the setup where I can reproduce it, the problem mostly disappears if I disable all my other extensions except for the Connector and uBlock origin. I don't think this is caused by any extension in particular, but is a race condition bug in Google Docs/Chrome that must eventually manifest in other ways in Chrome and cause doc desync issues, such that they will have to fix it.
I am out of ideas for how to debug it right now. If we update a google document in the backend and the client (browser-side google doc) doesn't receive/overwrites its contents with client-side version, there is nothing we can do.
The tentative solution is for users to use Firefox while waiting for Google to fix this.
I've finally managed to reliably reproduce it. I think it only happens on fairly fast and low-load machines.
To reproduce chrome needs to be set to reopen previous tabs after restarting the browser:
Ways to resolve:
I'll try reporting this upstream.