[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

[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

[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

[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

[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

[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

[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

[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

[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

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

Re: Bug 81720

[Michael Stahl]

On 23.08.22 13:12, Michael Stahl wrote:

On 19.08.22 15:41, Phillips Rogfield wrote:

Dear developers,

I would like to fix bug 81720 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


Basically when you insert a ReferenceMark, if you put the cursor at 
the edge of it (start or end), and type something, it will expand on 
the reference mark instead of writing it as a “normal text”.


You can find how to reproduce it in comment 22 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


I have set up my environment, but I’m not sure where is the code that 
“checks” if something is a ReferenceMark, if anything.


Can you point me in the right direction, please?


so firstly, while cross references are fields, the reference marks are 
not fields in Writer.


there are 2 different kinds of reference mark, both represented by a 
SwTextAttr with ID RES_TXTATR_REFMARK.


one has a dummy character in the text, CH_TXTATR_INWORD, and behaves 
similar to a field - it does not have an end position, so it cannot mark 
text, it only contains its dummy character.


the other has a start and end position, but no dummy character - this is 
the one you're concerned about.


these SwTextAttr all exist in a SwpHints array that is a member 
SwTextNode::m_pSwpHints, sorted in multiple different ways.


when editing the text, the hints start and end positions are adjusted in 
  SwTextNode::Update() and its base class SwContentIndexReg::Update() - 
it's rather complex code but i think you need to tweak these functions 
to fix the problem.


forgot one thing: bookmark positions already work in the way that you 
want reference marks to work, text is always inserted outside the 
bookmark - maybe you could find out how that is implemented in the 
Update functions.

Re: Bug 81720

[Michael Stahl]

On 19.08.22 15:41, Phillips Rogfield wrote:

Dear developers,

I would like to fix bug 81720 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


Basically when you insert a ReferenceMark, if you put the cursor at the 
edge of it (start or end), and type something, it will expand on the 
reference mark instead of writing it as a “normal text”.


You can find how to reproduce it in comment 22 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


I have set up my environment, but I’m not sure where is the code that 
“checks” if something is a ReferenceMark, if anything.


Can you point me in the right direction, please?


so firstly, while cross references are fields, the reference marks are 
not fields in Writer.


there are 2 different kinds of reference mark, both represented by a 
SwTextAttr with ID RES_TXTATR_REFMARK.


one has a dummy character in the text, CH_TXTATR_INWORD, and behaves 
similar to a field - it does not have an end position, so it cannot mark 
text, it only contains its dummy character.


the other has a start and end position, but no dummy character - this is 
the one you're concerned about.


these SwTextAttr all exist in a SwpHints array that is a member 
SwTextNode::m_pSwpHints, sorted in multiple different ways.


when editing the text, the hints start and end positions are adjusted in 
 SwTextNode::Update() and its base class SwContentIndexReg::Update() - 
it's rather complex code but i think you need to tweak these functions 
to fix the problem.

Re: Bug 81720

[Andrew Pitonyak]

Phil,

You surely do NOT need my approval :-)

I was just asking since it seems consistent with other things in libre office.

Now I am curious about a field as the last thing in a document.  :-)

Had not considered using ESC to put the cursor out of a field, on the surface 
it feels like a really smart solution, but to be clear, if the devs choose to 
simply have an adjacent chair always be outside the field I would not complain, 
it would solve the end of document problem but makes it more difficult to 
append text in a field or deal with a one character looking field.

The zero length field... Uggg. Had not considered that one.

I am very happy to see how thoroughly y'all are working to get a correct 
solution.

Andrew.

⁣Get BlueMail for Android ​

On Aug 19, 2022, 7:26 PM, at 7:26 PM, Phillips Rogfield  
wrote:
>Hello,
>
>You are right that by putting the cursor to the left it writes normal
>text. It only happens when you put the cursor to the right of the
>field.
>
>It is not necessary that the field is the last thing in a file. It is
>sufficient it is the last thing in a paragraph. In this case you won't
>be able to insert text after the field without expanding the field. At
>least it will be not so simple. You will have to press Enter, space,
>left arrow, backspace, right arrow, and type.
>
>I also noticed an exception: if you don't select anything, and do
>Insert
>-> Cross Reference ->  Set Reference, type a name, press Insert and
>then
>Close, it will insert an empty reference (which I have no idea why it
>differs conceptually from a bookmark?). This empty reference will be
>not
>modifiable: nor by putting the cursor to the left nor to the right, the
>
>text of the reference will stay empty.
>
>So exception aside, I think maybe a good compromise would be that, if
>the user put the cursor on the right of a field, and press "Esc", it
>will start to type outside of the field, without expanding the field?
>Would that work?
>
>Best,
>
>Phil
>
>On 19/08/2022 16:04, Andrew Pitonyak wrote:
>> The general expected behavior in libre office, at least for me, is
>> that if I place the cursor and start typing, that it will continue
>> using the same attributes and properties of the character directly to
>
>> the left of the cursor. So, if I have bold text, and I placed the
>> cursor to the left of the bold text and I type, it will not be bold,
>> it will be whatever is to the left of the cursor. If the cursor is
>> immediately to the right of the bold text however then it will be
>bold.
>>
>> In this case, I assume, but have not verified or checked in anyway, 
>> references are a field. So the intent of this is to make certain that
>
>> when the cursor is sitting directly to the left or right of, whatever
>
>> is typed does not end up inside of that field. One side effect of
>this
>> I expect, is that if you have a field with only one character you
>will
>> have no way of modifying the text inside the field unless there is
>> some special case when the text of the field is selected. I did not
>> even check, can I select the text in a field? So what if the
>selection
>> is partially in a field?
>>
>> I would never have considered this a bug, I would have just
>considered
>> it an extension of expected behavior. The annoying part is that if
>the
>> field is the last thing in a file you have no way to add text after
>> the field unless you do it programmatically, but that is also true
>> last I checked of text tables.
>>
>> I hope other contributors to comments in the bugs are correct that it
>
>> is an easy fix, but I am skeptical.
>>
>> Get BlueMail for Android <https://bluemail.me>
>> On Aug 19, 2022, at 9:41 AM, Phillips Rogfield
>
>> wrote:
>>
>> Dear developers,
>>
>> I would like to fix bug 81720
>> <https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.
>>
>> Basically when you insert a ReferenceMark, if you put the cursor
>> at the edge of it (start or end), and type something, it will
>> expand on the reference mark instead of writing it as a “normal
>text”.
>>
>> You can find how to reproduce it in comment 22
>> <https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.
>>
>> I have set up my environment, but I’m not sure where is the code
>> that “checks” if something is a ReferenceMark, if anything.
>>
>> Can you point me in the right direction, please?
>>
>> Best,
>>
>> Phil
>>
>> ​
>>

Re: Bug 81720

[Phillips Rogfield]

Hello,

You are right that by putting the cursor to the left it writes normal 
text. It only happens when you put the cursor to the right of the field.


It is not necessary that the field is the last thing in a file. It is 
sufficient it is the last thing in a paragraph. In this case you won't 
be able to insert text after the field without expanding the field. At 
least it will be not so simple. You will have to press Enter, space, 
left arrow, backspace, right arrow, and type.


I also noticed an exception: if you don't select anything, and do Insert 
-> Cross Reference ->  Set Reference, type a name, press Insert and then 
Close, it will insert an empty reference (which I have no idea why it 
differs conceptually from a bookmark?). This empty reference will be not 
modifiable: nor by putting the cursor to the left nor to the right, the 
text of the reference will stay empty.


So exception aside, I think maybe a good compromise would be that, if 
the user put the cursor on the right of a field, and press "Esc", it 
will start to type outside of the field, without expanding the field? 
Would that work?


Best,

Phil

On 19/08/2022 16:04, Andrew Pitonyak wrote:
The general expected behavior in libre office, at least for me, is 
that if I place the cursor and start typing, that it will continue 
using the same attributes and properties of the character directly to 
the left of the cursor. So, if I have bold text, and I placed the 
cursor to the left of the bold text and I type, it will not be bold, 
it will be whatever is to the left of the cursor. If the cursor is 
immediately to the right of the bold text however then it will be bold.


In this case, I assume, but have not verified or checked in anyway,  
references are a field. So the intent of this is to make certain that 
when the cursor is sitting directly to the left or right of, whatever 
is typed does not end up inside of that field. One side effect of this 
I expect, is that if you have a field with only one character you will 
have no way of modifying the text inside the field unless there is 
some special case when the text of the field is selected. I did not 
even check, can I select the text in a field? So what if the selection 
is partially in a field?


I would never have considered this a bug, I would have just considered 
it an extension of expected behavior. The annoying part is that if the 
field is the last thing in a file you have no way to add text after 
the field unless you do it programmatically, but that is also true 
last I checked of text tables.


I hope other contributors to comments in the bugs are correct that it 
is an easy fix, but I am skeptical.


Get BlueMail for Android <https://bluemail.me>
On Aug 19, 2022, at 9:41 AM, Phillips Rogfield  
wrote:


Dear developers,

    I would like to fix bug 81720
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.

Basically when you insert a ReferenceMark, if you put the cursor
at the edge of it (start or end), and type something, it will
expand on the reference mark instead of writing it as a “normal text”.

You can find how to reproduce it in comment 22
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.

I have set up my environment, but I’m not sure where is the code
that “checks” if something is a ReferenceMark, if anything.

Can you point me in the right direction, please?

Best,

Phil

​

Re: Bug 81720

[Andrew Pitonyak]

The general expected behavior in libre office, at least for me, is that if I 
place the cursor and start typing, that it will continue using the same 
attributes and properties of the character directly to the left of the cursor. 
So, if I have bold text, and I placed the cursor to the left of the bold text 
and I type, it will not be bold, it will be whatever is to the left of the 
cursor. If the cursor is immediately to the right of the bold text however then 
it will be bold.

In this case, I assume, but have not verified or checked in anyway,  references 
are a field. So the intent of this is to make certain that when the cursor is 
sitting directly to the left or right of, whatever is typed does not end up 
inside of that field. One side effect of this I expect, is that if you have a 
field with only one character you will have no way of modifying the text inside 
the field unless there is some special case when the text of the field is 
selected. I did not even check, can I select the text in a field? So what if 
the selection is partially in a field?

I would never have considered this a bug, I would have just considered it an 
extension of expected behavior. The annoying part is that if the field is the 
last thing in a file you have no way to add text after the field unless you do 
it programmatically, but that is also true last I checked of text tables.

I hope other contributors to comments in the bugs are correct that it is an 
easy fix, but I am skeptical.

⁣Get BlueMail for Android ​

On Aug 19, 2022, 9:41 AM, at 9:41 AM, Phillips Rogfield  
wrote:
>Dear developers,
>
>I would like to fix bug 81720
><https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.
>
>Basically when you insert a ReferenceMark, if you put the cursor at the
>
>edge of it (start or end), and type something, it will expand on the
>reference mark instead of writing it as a “normal text”.
>
>You can find how to reproduce it in comment 22
><https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.
>
>I have set up my environment, but I’m not sure where is the code that
>“checks” if something is a ReferenceMark, if anything.
>
>Can you point me in the right direction, please?
>
>Best,
>
>Phil
>
>​

Re: Bug 81720

[Ilmari Lauhakangas]

On 19.8.2022 16.41, Phillips Rogfield wrote:

Dear developers,

I would like to fix bug 81720 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


Basically when you insert a ReferenceMark, if you put the cursor at the 
edge of it (start or end), and type something, it will expand on the 
reference mark instead of writing it as a “normal text”.


You can find how to reproduce it in comment 22 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


I have set up my environment, but I’m not sure where is the code that 
“checks” if something is a ReferenceMark, if anything.


Can you point me in the right direction, please?


If you look at the file attached to the report (flat ODF), it has

text:name="fooname"/>foo


Grepping then with

git grep 'reference-mark-start'

yields interesting results like

xmloff/source/core/xmltoken.cxx:TOKEN( "reference-mark-start", 
  XML_REFERENCE_MARK_START ),


Hopefully it can help you.

I have no experience with the topic :)

Ilmari

Bug 81720

[Phillips Rogfield]

Dear developers,

I would like to fix bug 81720 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


Basically when you insert a ReferenceMark, if you put the cursor at the 
edge of it (start or end), and type something, it will expand on the 
reference mark instead of writing it as a “normal text”.


You can find how to reproduce it in comment 22 
<https://bugs.documentfoundation.org/show_bug.cgi?id=81720#c22>.


I have set up my environment, but I’m not sure where is the code that 
“checks” if something is a ReferenceMark, if anything.


Can you point me in the right direction, please?

Best,

Phil

​

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[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

[Libreoffice-bugs] [Bug 81720] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Julien Nabet  changed:

   What|Removed |Added

 CC||serval2...@yahoo.fr

--- Comment #21 from Julien Nabet  ---
Created attachment 157003
  --> https://bugs.documentfoundation.org/attachment.cgi?id=157003=edit
test with Win10 + LO 6.3.4

I gave a try to initial comment on Win10 with LO 6.3.4 (last stable LO version)

Is there something wrong in the attached file?

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Dieter Praas  changed:

   What|Removed |Added

   Hardware|x86-64 (AMD64)  |All
 OS|Linux (All) |All
Version|6.1.5.2 release |Inherited From OOo

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #20 from Adomas Venčkauskas  ---
Both bugs describe essentially the same problem. bug#123224 references Zotero
for why the bug is important, but the actual steps to reproduce do not require
it. Either bug is fine, as long as we get the attention of actual developers
(which this bug has unfortunately not seen for over 5 years).

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #19 from Juang Dse  ---
(In reply to David Lawrence from comment #17)
> Although marked as a duplicate, the report in 123224 provides a detailed
> description of the steps to reproduce this problem.

I agree. But I think this bug here describes the buggy situation somewhat more
concise and simpler, as it indeed does not depend on Zotero.

But no surprise, its importance to me comes also from its effect on Zotero. If
there is agreement that that is more important, anybody should feel free to
reverse the bug dependence.

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Dan John  changed:

   What|Removed |Added

 OS|All |Linux (All)
   Hardware|All |x86-64 (AMD64)
Version|Inherited From OOo  |6.1.5.2 release

--- Comment #18 from Dan John  ---
Hi, I've been dealing with the bug 123224 for a long time with Zotero
extension.
It threatens to corrupt my cited documents as I'm working on them as references
get mistakenly interfered with and then when Zotero updates its fields it
either deletes intended normal text without user easily noticing, or
alternately disables automatic updates to field which negates updates from
database. Problematic for larger projects like my dissertation which is what
I'm using it for :)
I love the Libreoffice and Zotero combination, it would be great if this was
fixed for my piece of mind :)

Reproduction instructions / screenshot: https://pasteboard.co/IIGwHe5.png

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #17 from David Lawrence  ---
(In reply to Juang Dse from comment #15)
> (In reply to Adomas Venčkauskas from comment #14)
> > Could we bump the importance of this bug to something higher. Bug
> > https://bugs.documentfoundation.org/show_bug.cgi?id=123224 was marked as
> > high by Dieter Praas due to issues this creates for referencing software
> > including Mendeley and Zotero.
> 
> I agree. This is a serious issue for all cross-referencing, so the priority
> should definitely go up.
> 
> This not only slows you down (comment 2), but really turns anybody off who
> tries to switch from other software to LO.

Although marked as a duplicate, the report in 123224 provides a detailed
description of the steps to reproduce this problem.

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #16 from David Lawrence  ---
Please make this a priority. An earlier request for work on this mentioned that
this bug causes problems with *improving* the way Zotero interacts with LO.
However, this bug as it exists now makes the existing Zotero interactions with
LO seriously inconvenient. Any edits of my LO Writer document that are too near
a Zotero reference will foul the document's reference functions. I found a
detailed description of the steps to reproduce this in bug#123224 that was
marked as a duplicate of this.

Please understand that this is a serious inconvenience to academic writing that
includes citations, references, and a bibliography.

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #15 from Juang Dse  ---
(In reply to Adomas Venčkauskas from comment #14)
> Could we bump the importance of this bug to something higher. Bug
> https://bugs.documentfoundation.org/show_bug.cgi?id=123224 was marked as
> high by Dieter Praas due to issues this creates for referencing software
> including Mendeley and Zotero.

I agree. This is a serious issue for all cross-referencing, so the priority
should definitely go up.

This not only slows you down (comment 2), but really turns anybody off who
tries to switch from other software to LO.

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Juang Dse  changed:

   What|Removed |Added

   Severity|minor   |normal

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #14 from Adomas Venčkauskas  ---
Could we bump the importance of this bug to something higher. Bug
https://bugs.documentfoundation.org/show_bug.cgi?id=123224 was marked as high
by Dieter Praas due to issues this creates for referencing software including
Mendeley and Zotero.

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #13 from Juang Dse  ---
*** Bug 126125 has been marked as a duplicate of this bug. ***

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Juang Dse  changed:

   What|Removed |Added

 CC||nalimi...@club.fr

--- Comment #12 from Juang Dse  ---
*** Bug 64361 has been marked as a duplicate of this bug. ***

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Juang Dse  changed:

   What|Removed |Added

 CC||adomas@gmail.com

--- Comment #11 from Juang Dse  ---
*** Bug 123224 has been marked as a duplicate of this bug. ***

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #10 from Juang Dse  ---
bug still there.

Version: 6.2.5.2
Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: gtk2; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #9 from QA Administrators  ---
Dear Juang Dse,

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

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #8 from Juang Dse  ---
bug still there, but modified.

inserting the cross-reference now leads to the text

"foonew textfoonew textfoonew text"

Version: 6.0.4.2
Build ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf
CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: gtk2; 
Locale: en-US (en_US.UTF-8); Calc: group


With the current 6.1 dev version I get

" fooname"

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #7 from QA Administrators  ---
** 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

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Dieter Praas  changed:

   What|Removed |Added

 Blocks||107905


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107905
[Bug 107905] [META] Cross-references bugs and enhancements
-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #6 from Juang Dse  ---
bug still there.

LibreOffice version 5.3.3 / Linux

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #5 from QA Administrators  ---
** 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.2.7 or 5.3.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-20170522

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Juang Dse  changed:

   What|Removed |Added

 CC||juang...@gmail.com

--- Comment #4 from Juang Dse  ---
bug still there. Now I even get the text

foonew textfoonew textfoonew text

LibreOffice version 5.1.2.2
Linux 3.16.0-38-generic x86_64 GNU/Linux

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #3 from tommy27  ---
** 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.5 or 5.1.2 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: 2016-04-16

-- 
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] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Michael Stahl mst...@redhat.com changed:

   What|Removed |Added

 Attachment #103404|text/plain  |application/vnd.oasis.opend
  mime type||ocument.text-flat-xml

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

[Libreoffice-bugs] [Bug 81720] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

Joel Madero jmadero@gmail.com changed:

   What|Removed |Added

   Hardware|Other   |All
 Status|UNCONFIRMED |NEW
   Severity|normal  |minor
   Priority|medium  |low
 CC||jmadero@gmail.com
Version|4.2.4.2 release |Inherited From OOo
 Ever confirmed|0   |1

--- Comment #2 from Joel Madero jmadero@gmail.com ---
Confirmed:
Ubuntu 14.04 x64
LibreOffice 3.3 (inherited from OOo) -- updating version (version is oldest
confirmed version, not latest)

New - confirmed
Minor - won't prevent high quality and/or professional work but can slow you
down
Low - been around for ages, once you know it's happening relatively easy
workaround

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

[Libreoffice-bugs] [Bug 81720] EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

--- Comment #1 from Juang Dse juang...@gmail.com ---
additionally, the text 'foonew text' is insert not only once but three times.

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

[Libreoffice-bugs] [Bug 81720] New: EDITING: setting cross-reference still active after closing

[bugzilla-daemon]

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

  Priority: medium
Bug ID: 81720
  Assignee: libreoffice-bugs@lists.freedesktop.org
   Summary: EDITING: setting cross-reference still active after
closing
  Severity: normal
Classification: Unclassified
OS: All
  Reporter: juang...@gmail.com
  Hardware: Other
Status: UNCONFIRMED
   Version: 4.2.4.2 release
 Component: Writer
   Product: LibreOffice

Created attachment 103404
  -- https://bugs.freedesktop.org/attachment.cgi?id=103404action=edit
file with cross-reference

1. type 'foo'
2. type Ctrl-a
2. Insert-Crossreference, Set Reference, Name: fooname, Insert, Close
3. type Esc
4. type 'new text'
5. Insert-Crossreference, Insert Reference, Name: fooname, Insert Reference to:
Reference

will insert 'foonew text'.

Alternatively, load the attached file foo.fodt and

1. place the cursor at the end
2. type 'n', Ctrl-z

continue from 4.

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