[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 refe

2023-05-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

Matti Tyrväinen  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |ma...@uef.fi
   |desktop.org |

--- Comment #39 from Matti Tyrväinen  ---
Picking this up once more as I have some time to throw at it again. Patchset 7
solves the failing test, just need to iron out some small kinks like the whole
program crashing when trying to reproduce the original bug ;)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-03-14 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

Matti Tyrväinen  changed:

   What|Removed |Added

 Status|ASSIGNED|NEW
   Assignee|ma...@uef.fi|libreoffice-b...@lists.free
   ||desktop.org

--- Comment #38 from Matti Tyrväinen  ---
I'm reverting the status to NEW in the hope that someone else will pick it up
as I'm currently unable to move forward with the patch in a timely manner. The
proposed patch *should* be enough to fix the issue, but, as it makes the
existing tests fail in an unexpected way, I can not recommend using it as-is to
avoid possible document-corrupting side-effects.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-02-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

ma...@uef.fi changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |ma...@uef.fi
   |desktop.org |
 Status|NEW |ASSIGNED

--- Comment #36 from ma...@uef.fi ---
I've requested a code review for making Reference Marks behave like "nested
attributes" eg. Hyperlinks (ie. as described by Adomas Venčkauskas).

https://gerrit.libreoffice.org/c/core/+/146941

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-02-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #35 from ma...@uef.fi ---
Still present on LO 7.5. As noted above, it hampers usage enough to steer users
from LO to Word et al. 

Another workaround is to use the insert mode (via the "Insert" key on the
keyboard) to prevent the cursor from entering the ReferenceMark in the first
place. This doesn't work if the ReferenceMark is at the very end of a
paragraph, but can be helpful elsewhere.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-01-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

V Stuart Foote  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=15 |
   |3085|

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-01-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

Robert Großkopf  changed:

   What|Removed |Added

 CC||rob...@familiegrosskopf.de

--- Comment #34 from Robert Großkopf  ---
*** Bug 153085 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-01-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

V Stuart Foote  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3085

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-01-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

V Stuart Foote  changed:

   What|Removed |Added

URL||https://ask.libreoffice.org
   ||/t/cannot-exit-the-cross-re
   ||ference/45964/2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2023-01-13 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #33 from Daniel T.  ---
It is difficult to believe that this bug remains unresolved for such a long
time, since 2016! This is a constant irritation to anyone who used LO
professionally and academically, greatly affecting the workflow and breaking
the creative writing process. 

Here is a report from LO community:
https://ask.libreoffice.org/t/cannot-exit-the-cross-reference/45964/2

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2022-05-18 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #32 from thebudge...@gmail.com ---
Can we fix this? I have this bug with Zotero and it is very frustrating.

see:
https://forums.zotero.org/discussion/94871/cannot-leave-citation-field-in-libreoffice-writer

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2022-04-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #31 from ds  ---
This bug is still effecting me on the LO packaged by the linux distro I use for
academic writing with zotero, and from threads on the zotero forum I see it is
effecting others as well. This adds a considerable inconvenience for using the
software for professional purposes despite some workarounds.

The difficulty and time required to fix it have been made clear earlier in the
thread, nevertheless I thought I would comment to confirm that this is still
effecting LO users using reference managers for professional writing.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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 refe

2020-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #30 from Julien Nabet  ---
(In reply to Adomas Venčkauskas from comment #29)
> ...
> Having said that, getting the attention of the right developers for this
> would be the most time efficient course of action and provide a huge
> improvement in usability for a large and passionate chunk of LibreOffice's
> userbase, who otherwise get edged to Word exactly for such minor annoyances.

Just consider the number of existing bugs declared on Bugzilla + priorities and
compare with few devs (knowing that some work now for Collabora and so are more
focused into their specific features sold by this company, like online
collaboration), you'll understand why it's not fixed yet.
So yes, for a first bug, it may take time for you but once it'll be done, you
may be able to tackle other bugs far more quickly since build/debug env will be
already installed! :-)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #29 from Adomas Venčkauskas  ---
(In reply to Julien Nabet from comment #28)
> (In reply to Adomas Venčkauskas from comment #27)
> > The bug is still present and highly bothersome for reference manager such as
> > Zotero or Mendeley users, of which there are tens (if not hundreds) of
> > thousands who use LibreOffice. I am certain this is 1 or 2 line change and
> > we just need to get the eyes of the right developers to get it fixed. Could
> > someone who does bug triage reach out to the right people here?
> 
> Since you seem confident about the fact it would just need a 1 or 2 lines
> change in the code, I propose you to give it a try.
> Here's a start link to start contributing in dev part:
> https://wiki.documentfoundation.org/Development/GetInvolved
> (some devs may help you if necessary on forum or IRC)

While I appreciate the idea, a 1 or 2 line fix for someone who is involved with
the codebase, works on it every day and knows the code inside out takes
anywhere from 15 minutes to an hour to make. For someone who does not have the
build and development environment setup and has never looked at the codebase it
could mean days or weeks, and also possibly hours wasted of those same
developers, providing help via IRC and mailing lists on how to set this whole
thing up and figure out where the code related to the features is. While this
is an important issue for Zotero, it is just an important for Document
Foundation if they are at all trying to be a serious alternative to Microsoft
Word, where this works as expected.

Having said that, getting the attention of the right developers for this would
be the most time efficient course of action and provide a huge improvement in
usability for a large and passionate chunk of LibreOffice's userbase, who
otherwise get edged to Word exactly for such minor annoyances.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #28 from Julien Nabet  ---
(In reply to Adomas Venčkauskas from comment #27)
> The bug is still present and highly bothersome for reference manager such as
> Zotero or Mendeley users, of which there are tens (if not hundreds) of
> thousands who use LibreOffice. I am certain this is 1 or 2 line change and
> we just need to get the eyes of the right developers to get it fixed. Could
> someone who does bug triage reach out to the right people here?

Since you seem confident about the fact it would just need a 1 or 2 lines
change in the code, I propose you to give it a try.
Here's a start link to start contributing in dev part:
https://wiki.documentfoundation.org/Development/GetInvolved
(some devs may help you if necessary on forum or IRC)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-06-05 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #27 from Adomas Venčkauskas  ---
The bug is still present and highly bothersome for reference manager such as
Zotero or Mendeley users, of which there are tens (if not hundreds) of
thousands who use LibreOffice. I am certain this is 1 or 2 line change and we
just need to get the eyes of the right developers to get it fixed. Could
someone who does bug triage reach out to the right people here?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-05-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

Julien Nabet  changed:

   What|Removed |Added

 OS|Mac OS X (All)  |All

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-05-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

CRP  changed:

   What|Removed |Added

 OS|All |Mac OS X (All)

--- Comment #26 from CRP  ---
I have also been experiencing this bug in conjunction with Zotero on MacOS.

It works like this:

1. Insert Zotero citation.
2. Begin typing (all is fine; the field stays intact).
3. Delete what I just typed and type again and this becomes part of the field.

So, the act of deleting up to the edge of the field (but not into it)
compromises the edge of the field and subsequent text becomes part of it,
causing an error.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-01-09 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

Xisco Faulí  changed:

   What|Removed |Added

 CC||xiscofa...@libreoffice.org
   Priority|high|medium

--- Comment #25 from Xisco Faulí  ---
Setting priority to normal. it was set to low in the past, bumping it from low
to normal, not from low to high, no reason for that

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-01-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #24 from Adomas Venčkauskas  ---
(In reply to sdc.blanco from comment #23)
> 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.)

Correct!

> 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).

No, being able to modify ReferenceMarks is actually both desirable and crucial
to the functionality of reference managers. However that should not be easy to
do accidentally. For reference, Zotero and Mendelay does not have similar
problems in Word, where Word fields are used. I.e. you can edit the field text
if you deliberately place the cursor inside them, but placing the cursor on
either edge of the field does not edit it. The same behaviour in LibreOffice
for ReferenceMarks would be ideal.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-01-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

--- Comment #23 from sdc.bla...@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.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[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 refe

2020-01-08 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81720

V Stuart Foote  changed:

   What|Removed |Added

   Priority|low |high
 CC||sdc.bla...@youmail.dk
Summary|EDITING: setting|After setting a
   |cross-reference still   |cross-reference object from
   |active after closing|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)

--- Comment #22 from V Stuart Foote  ---
Clean STR from dupe bug 123224

Steps to Reproduce:
1. Insert some text in Writer
2. Select a portion of the text -> Insert -> Cross-Reference -> Set Reference,
set some text in the "Name" field and click "Insert"
3. Ensure field shading is enabled
4. Place the cursor outside the newly created ReferenceMark, then place it on
the edge of the ReferenceMark, type something.

Actual Results:
The ReferenceMark is extended

Expected Results:
The newly typed text remains outside of the ReferenceMark

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs