Created attachment 105104 [details]
One of the affected documents
Enumerating all text fields of some writer documents using
the first n fields are reported as com.sun.star.text.textfield.PageNumber but they actually are com.sun.star.text.textfield.User
Iterating the document paragraph by paragraph this does not happen
The behavior can be reproduced under Linux and Windows using Open JDK 1.7 and Oracle Java 1.7, Writer 184.108.40.206 and 220.127.116.11
Inverting the access using getTextFieldMasters() the field master exists but the DependentTextFields property has less entries than expected.
Te fact is related with tables - removing the tables everything is alright.
Can you give more detailed steps for reproduction, so any random QA team member without prior experience with scripting can test this? Change back to UNCONFIRMED after supplying the information.
Created attachment 109406 [details]
An affected document with a macro to show the error
Added a macro called "TestCase" that lists the ServiceNames of all userfields in the document. just call the macro. After a wile a message box shows up and the first twenty lines will show "PageNumber"
(In reply to Stefan Ziel from comment #4)
> Created attachment 109406 [details]
> An affected document with a macro to show the error
> Added a macro called "TestCase" that lists the ServiceNames of all
> userfields in the document. just call the macro. After a wile a message box
> shows up and the first twenty lines will show "PageNumber"
Win 7 64-bit Version: 18.104.22.168.alpha2+
Build ID: b021b5983c62e266b82d9f0c5c6d8d8900553827
TinderBox: Win-x86@39, Branch:master, Time: 2014-11-12_01:10:08
Adjusting importance as per https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Severity. No "crashes, loss of data, severe memory leak, major loss of function", but "regular issue, some loss of functionality under specific circumstances".
(also component: writer as that is where it needs to be fixed)
** 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)
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!
This is not a bug.
The order of the fields returned from getTextFields enumeration is not related to the order of the paragraphs. It returns the fields in an implementation dependent order.
(In reply to Oliver Specht (CIB) from comment #9)
> This is not a bug.
> The order of the fields returned from getTextFields enumeration is not
> related to the order of the paragraphs. It returns the fields in an
> implementation dependent order.