Download it now!
Bug 118459 - Cross references to footnotes are not updated when inserting a new footnote with a lower number
Summary: Cross references to footnotes are not updated when inserting a new footnote w...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.4.2 release
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fields-Cross-Reference
  Show dependency treegraph
 
Reported: 2018-06-29 17:11 UTC by Claudi
Modified: 2019-09-07 05:58 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Claudi 2018-06-29 17:11:46 UTC
I have noticed that cross references to footnotes are not updated when I insert a new footnote with a lower number. Let me explain this scenario. 

I start with a document with three lines:

    This is the first line
    This is the second line
    This is the third line

Then I do these steps:

 1. Insert a footnote on the second line, with text "Footnote A"
 2. Insert a cross-reference to that footnote on the third line and format the number as superscript.

After this, I have the following text (NOTE: I use the caret ^ to depict a superscript)

    This is the first line 
    This is the second line ^1
    This is the third line ^1

And at the bottom of the page, I have this footnote:

    1 Footnote A

Good, so far. Now I want to put a footnote on the first line, with text "Footnote B". Then, I get:

    This is the first line ^1
    This is the second line ^2
    This is the third line ^1

As you can see, the third line's cross reference is not updated. At the bottom of the page I have the expected footnotes:

    1 Footnote B
    2 Footnote A

The footnote references should be updated whenever the footnotes change. I confirm this unexpected behaviour even after Tools>Update>Update All.
Comment 1 Roman Kuznetsov 2018-06-29 18:46:45 UTC
confirmed for LO 6.0.4.2
Comment 2 Xisco Faulí 2018-07-02 23:43:19 UTC
> Good, so far.

@Claudi, Could you please add the document up to this point and it makes it easier for triage?
Comment 3 Xisco Faulí 2019-02-07 20:05:07 UTC
(In reply to Roman Kuznetsov from comment #1)
> confirmed for LO 6.0.4.2

@Roman, Could you please help with that ?
Comment 4 Roman Kuznetsov 2019-02-07 20:31:05 UTC
(In reply to Xisco Faulí from comment #3)
> (In reply to Roman Kuznetsov from comment #1)
> > confirmed for LO 6.0.4.2
> 
> @Roman, Could you please help with that ?

I can't repro it in

Version: 6.3.0.0.alpha0+
Build ID: cec3fe24dd4569bf04b13e0284823bad129dbb86
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-02-02_03:18:07
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

need more testing
Comment 5 QA Administrators 2019-08-07 04:47:12 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2019-09-07 05:58:40 UTC
Dear Claudi,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp