Created attachment 79024 [details] Document to illustrate the problem (does not require Zotero) The Zotero citation management tool inserts complex fields through a LO/OO plug-in. These fields can appear in various forms, but typically they look like "(Author YYY)", while the field itself contains many properties, like this: "ZOTERO_ITEM CSL_CITATION{"prop1":"val1", ...}". The problem can be reproduced without having Zotero installed. In the attached document, text typed after these fields is included into the field (with a grey background). This does not happen with text typed immediately after inserting the field: it only happens when one writes something and then goes back to the end of the field (not visible on this document, since one needs Zotero for this). This behaviour is problematic since Zotero will erase all the text typed in these fields when e.g. changing citation styles or refreshing the references. Then user text can be lost. More generally, I don't think it makes sense to allow changing the text of the field by typing *at the end* of it. Even if typing text in the middle of the field was deemed useful, typing text after it should always result in a normal text being inserted. I have not been able to reproduce this with fields inserted from LO itself, but I'm not very familiar with this mechanism. I don't think the bug can come from Zotero. Please note that Zotero is a very valuable addition to LO for academics, making it a credible alternative to the MS Word/EndNote couple. [This is reproducible with LO 4.0.2.2 but is a very old issue.]
Just "me too". I use Mendeley (based on Zotero) and also sometimes get hit by this issue. Editing document with higlighted fields helps to see when issue appears and not continue editing till type/delete dance stops editing of the field content. Still more robust or user friendly approach would be nice.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.1 or preferably 5.0.2.2 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-10-14
Works on Win7 Pro 64bit, with LibreOffice 5.0.2.2 and Zotero 4.0.28.7 and its LO Integration 3.5.10 :-)
Sorry, but it still happens here on Linux with LO 5.0.2.2. You need to enter some text, remove it, and type more to reproduce the problem.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
Still present in LO 5.2.
This bug was never confirmed by a third person. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Yes, it's been confirmed by one person other than me. It still happens with LO 5.3.0.3 (I don't see a reason to think it would have been fixed in 5.3.4).
(In reply to Milan Bouchet-Valat from comment #8) > Yes, it's been confirmed by one person other than me. It still happens with > LO 5.3.0.3 (I don't see a reason to think it would have been fixed in 5.3.4). I don't see the third person you're mentioning... Anyway, let leave it as NEW...
(In reply to Xisco Faulí from comment #9) > (In reply to Milan Bouchet-Valat from comment #8) > > Yes, it's been confirmed by one person other than me. It still happens with > > LO 5.3.0.3 (I don't see a reason to think it would have been fixed in 5.3.4). > > I don't see the third person you're mentioning... Anyway, let leave it as > NEW... That was comment 1
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in 6.0.4.2.
Isn't bug 123224 a DUPLICATE of this ? It seems to replicate what is being described here ?
*** Bug 123224 has been marked as a duplicate of this bug. ***
*** Bug 126125 has been marked as a duplicate of this bug. ***
I confirm it with Version: 6.2.5.2 (x64) Build-ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded Steps to reproduce 1. Open a new document 2. Insert Zotero citation 3. Type something after citation (text doesn't extend citation) 4. Delete text after citation or put cursor at the end of citation 5. Type text Result: text extends citation
I wonder if the duplicate bug 123224 is not the simpler one. It is unrelated to Zotero, doesn't require any attachment, and seems to nail down exactly what is happening. So instead of having bug 123224 being a duplicate of this one, should it not be vice versa?
*** This bug has been marked as a duplicate of bug 81720 ***