Google docs zotero causing the window to come in focus when updating is finished
Hello,
The google docs zotero plugin, when it finishes updating the document, it brings the window to focus.
This is disruptive in the workflow. Because updating takes a while, I switch to other windows to keep working, and all of a sudden I get the window popped back to the front.
Please change the functionality to be similar to how zotero works in Word.
Thank you
The google docs zotero plugin, when it finishes updating the document, it brings the window to focus.
This is disruptive in the workflow. Because updating takes a while, I switch to other windows to keep working, and all of a sudden I get the window popped back to the front.
Please change the functionality to be similar to how zotero works in Word.
Thank you
See: https://forums.zotero.org/discussion/73163/improve-citation-update-speed-in-microsoft-word#latest
Libreoffice Writer 6.3.0.4 in Manjaro linux
Word 2013 in Windows 7
that's why I found it disruptive and annoying when happened in Google docs as I descrived above.
Think of it this way. If I want the process to finish as quickly as possible, then I will simply wait and look at the progress bar to finish. No need to refocus the window.
If I want to do some quick tasks while I'm waiting for my process to finish, I will switch windows and work on that, and come back when I'm ready to work again in a few seconds. If I start working on something else (e.g. go back into checking the journal article) and suddenly the document processor pops up in my face, it will be disruptive.
Is it maybe possible in the future to add an option to disable window refocusing please?
@MavropaliasG Yes, it seems that the focus management generally works best on macOS. We'll keep this in mind.
Anyway, thanks. It's not more than an inconvenience, but it is very confusing when I'm genuinely trying to figure out if a document is done being updated!
(Regarding focus, yes it works well on Mac. But one oddity is that if I happen to have clicked into another Word document window while something is going on, it ALWAYS has an error by the time the process finishes, even if I click back immediately. It's fine just to not do that, but technically speaking it's not really focusing the right window there either, just the app, and confused by any inconsistency when it gets back there.)
We actually have an indeterminate progress bar from Zotero for document refresh on Linux and Windows, but we could not make it work in macOS without some actually pretty bad window focusing behaviours in there. This was a while back, so I don't remember the specifics, but we decided that the behaviour was so annoying that it's better to have no progress bar at all for document refreshing. We might revisit this once macOS Catalina ships.
Really, the issue on the Mac is just genuinely not knowing whether the process is going or not. It's clear when it completes because the bibliography is generated, but with a very long document it might take several minutes of nothing happening before it even seems to do anything, so it's ambiguous. (I've spent many minutes watching the first few cites in the document hoping to see some of them replaced as it processes them.)
So yes, if this can be revisited later that would be great, but it's not limiting functionality or anything so I understand if it's not a priority. OK, I'll do that now. (Been busy preparing a draft of my thesis.)
Update: nevermind! I tried doing this with debug logging enabled, and now it seems to work. I wonder what is different. It did once refocus to the wrong window (I was working in Doc1, adding a cite to Doc1, and then clicked over to Doc2 while the popup was open, and then back to Doc1, but when it correctly inserted the cite in Doc1, it also refocused Doc2. But aside from that oddity I'm not getting the "can't insert citation" error I've seen before in that context. If I figure out how to reproduce it I'll post with a Debug ID on the forums.
Other threads suggested this might be if the Zotero stand-alone window has been minimised, but in my case this bug occurs even if it is not, in about 80% of the times (can't reliably figure out when it does not!).
Can this be reproduced and maybe fixed? I used Firefox 78.6.1 and Zotero 5.0.94 on WIndows for the above report.