Bug 107628

Summary:	Filesave: Table position wrong on RT (filesave and fileopen) in LO, behind chart in DOC and overlapping chart in DOCX (anchor changed?) - position OK in MSO
Product:	LibreOffice	Reporter:	Timur <timur>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	libreoffice, lo_bugs, telesto, xiscofauli
Priority:	medium	Keywords:	bibisected, bisected, filter:doc, regression
Version:	4.2.0.4 release
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=128207 https://bugs.documentfoundation.org/show_bug.cgi?id=142381
Whiteboard:
Crash report or crash signature:		Regression By:
Bug Depends on:
Bug Blocks:	112700, 116112, 120466, 120468
Attachments:	Test ODT with chart and table Test ODT compare with DOC - chart table.png details of bibisect in 43max repository Test compared in LO 6.4+ as ODT/DOC/DOCX and MSO 2016 as DOC/DOCX

Description Timur 2017-05-04 15:17:55 UTC

Created attachment 133073 [details]
Test ODT with chart and table

Open test ODT with chart and table and save as DOC, reopen DOC.
Table position is wrong, it overlapped chart, maybe because anchor changed (or not, Bug 37002 and Bug 49179 are closed).
Looks like it was OK up to 4.1.6 and then wrong since 4.2.0, first table was behind and later in front of chart. 
I guess bibisect would be useful.

Comment 1 Timur 2017-05-04 15:19:29 UTC

Created attachment 133075 [details]
Test ODT compare with DOC - chart table.png

Comment 2 Timur 2017-05-04 15:21:50 UTC

*** Bug 107623 has been marked as a duplicate of this bug. ***

Comment 3 Telesto 2017-05-04 17:07:57 UTC

Setting to NEW. I can confirm, see bug 107623

Comment 4 Terrence Enger 2017-05-12 03:34:01 UTC

Created attachment 133253 [details]
details of bibisect in 43max repository

Working on debian-stretch in the bibisect-43max repository, I conclude

          commit    s-h
          --------  --------
    good  e4444f5a  c7190108
    bad   af102580  6e61ecd0

I am removing keyword bibisectRequest and adding bisected.

Comment 5 Xisco Faulí 2017-05-12 20:12:50 UTC

Regression introduced by:

author	Armin Le Grand <alg@apache.org>	2014-03-19 16:17:02 (GMT)
committer	Miklos Vajna <vmiklos@collabora.co.uk>	2014-03-28 13:31:08 (GMT)
commit 6e61ecd09679a66060f932835622821d39e92f01 (patch)
tree 4ce71adaa6da133cab09660b3efc1341104022a2
parent c7190108f02921868cb617040aebdb2d22c02c1f (diff)
Merge back branch alg_writerframes to trunk

Adding Cc: to Armin Le Grand

Comment 6 Timur 2018-10-10 14:57:11 UTC Comment hidden (obsolete)

Repro 6.2+. Armin, can you please check?

Comment 7 QA Administrators 2019-10-11 02:35:30 UTC Comment hidden (obsolete)

Dear Timur,

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

Comment 8 Timur 2019-10-11 06:38:04 UTC

Created attachment 154917 [details]
Test compared in LO 6.4+ as ODT/DOC/DOCX and MSO 2016 as DOC/DOCX

(In reply to Timur from comment #6)
> Repro 6.2+. 

Now with 6.4+ I did a proper test, saved ODT as DOC and DOCX and opened those both in LO and MSO. 
Seems that LO opens wrong both round-tripped files (table missing in DOC and overlapping chart in DOCX, which if different from before when reported) while MSO opens table with chart right (MSO shows chart from DOCX wrong but that another issue). 

So this sound now more as fileopen (it's own file) than filesave but nevermind until we have a fix.

Comment 9 Timur 2019-10-11 06:50:32 UTC

Note: another issue with DOC/DOCX is number of footer rows but that's related to bug 94801.

Comment 10 Timur 2020-01-17 09:21:37 UTC Comment hidden (obsolete)

Regression from 4.2. Repro 6.5+.

Comment 11 Armin Le Grand 2022-01-05 09:47:27 UTC

This commit was developed for another code base, and not merged by me. For complex changes like this, side-effects are to be expected; sadly I dont't have the cycles to deal with all the fallout. Un-Ccing myself for the while.

Comment 12 Timur 2022-01-05 14:59:00 UTC

Just to note that this regression from 4.2 is still repro in 7.3 master.

Comment 13 Justin L 2023-05-27 16:57:50 UTC


*** This bug has been marked as a duplicate of bug 76022 ***