[Libreoffice-bugs] [Bug 81720] After setting a cross-reference object from Fields dialog (or API calls), it can incorrectly receive edit cursor from document canvas during editing corrupting both reference field and document text (STR comment 22)

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Wed Jan 8 16:30:46 UTC 2020


https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #23 from sdc.blanco at youmail.dk ---
(In reply to Julien Nabet from comment #21)
> Is there something wrong in the attached file?
Easy to fix.  

1. Place cursor after foo.  
2. Type anything (e.g., space). (still looks ok)
3. Delete back to edge of (but outside of) ReferenceMark.
4. start typing anything again.  (you should be "rewarded" with an expanding
ReferenceMark).

(In reply to V Stuart Foote from comment #22)
> 4. Place the cursor outside the newly created ReferenceMark, then place it
> on the edge of the ReferenceMark, type something.
Only at "end" edge of ReferenceMark.  Can type at beginning of ReferenceMark
without problem.

Can repro with:

Version: 6.5.0.0.alpha0+ (x64)
Build ID: 035c7717c135c66c0ec025500b73ae9c13b7c586
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: da-DK (en_DK); UI-Language: en-US
Calc: threaded

I believe the critical problem here is not just visual.  
The "expanding" field means that the value of the Reference Name is changing
(which is why the Zotero users are concerned.)

Have there also been complaints about the fact that one can click inside the
ReferenceMark (shaded field) and then type away (i.e., changing the value)?
That would seem like a "cousin" to this problem.  There does not seem like
there is a way to protect ReferenceMarks (or variable fields).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20200108/aaa48b92/attachment.htm>


More information about the Libreoffice-bugs mailing list