Created attachment 133178 [details] sample Steps: 1) Open attached document 2) Notice that the page number field, the number 1, doesnt have deletion track changes assigned to it Version: 5.4.0.0.alpha0+ Build ID: 74ccd02eda2d6325a27266fd935aba29b3d75020 CPU threads: 2; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-04-27_23:51:14 Locale: en-US (en_US.UTF-8); Calc: group LibreOffice 3.3 to 4.0 did know that track changes happened on the line, as it did have the track changes vertical line in the margins, but it also didnt show that the page number field had a deletion track changes on it. The relevant xml code from the /word/document.xml file is below. <w:del w:id="0" w:author="jay18" w:date="2017-05-09T08:20:00Z"> <w:r w:rsidDel="00476164"> <w:fldChar w:fldCharType="begin" /> </w:r> <w:r w:rsidDel="00476164"> <w:delInstrText xml:space="preserve"> PAGE \* MERGEFORMAT </w:delInstrText> </w:r> <w:r w:rsidDel="00476164"> <w:fldChar w:fldCharType="separate" /> </w:r> <w:r w:rsidDel="00476164"> <w:rPr> <w:noProof /> </w:rPr> <w:delText>1</w:delText> </w:r> <w:r w:rsidDel="00476164"> <w:rPr> <w:noProof /> </w:rPr> <w:fldChar w:fldCharType="end" /> </w:r> </w:del>
Created attachment 133179 [details] word vs 4.0 vs 5.4
Repro with: Version: 5.4.0.0.alpha1+ Build ID: 970b431f1a7b6b96c4c9536657ce4fe9d8f5b585 CPU threads: 4; OS: Windows 6.2; UI render: default; TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-11_23:07:53 Locale: en-US (nl_NL); Calc: single
** 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
confirmed still a problem in 6.2. Bibisect43all suggests it is inherited.
The import problem was fixed as part of the export problem, see first patch in Bug 70234 (https://git.libreoffice.org/core/+/d160bca0dcb80f1b517b79221d5c3a43bbad8639%5E%21)