Bug 131735 - Fileopen DOC: misplaced floating table (vertical position relative to page)
Summary: Fileopen DOC: misplaced floating table (vertical position relative to page)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4 all versions
Hardware: All All
: low normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:doc, filter:docx
Depends on:
Blocks:
 
Reported: 2020-03-31 10:54 UTC by Timur
Modified: 2022-04-01 08:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
DOC compared MSO LO (103.95 KB, image/png)
2020-03-31 10:54 UTC, Timur
Details
DOCX from DOC saved in MSO (135.46 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2020-03-31 10:55 UTC, Timur
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2020-03-31 10:54:30 UTC
Created attachment 159183 [details]
DOC compared MSO LO

DOC attachment 159136 [details] opens with misplaced floating table (vertical position relative to page), as attached.
Similar issue if resaved in MSO as DOCX.
If floating wrap around turned off in MSO, it positions as in LO.
Comment 1 Timur 2020-03-31 10:55:19 UTC
Created attachment 159184 [details]
DOCX from DOC saved in MSO
Comment 2 Xisco Faulí 2020-03-31 16:18:21 UTC
Reproduced in

Version: 7.0.0.0.alpha0+
Build ID: 169a10f0e4680814145b668c6320be04038d7a89
CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Version: 5.2.0.0.alpha1+
Build ID: 5b168b3fa568e48e795234dc5fa454bf24c9805e
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; 
Locale: ca-ES (ca_ES.UTF-8)

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e

in previous versions, it seems even worse
Comment 3 QA Administrators 2022-04-01 03:39:35 UTC Comment hidden (obsolete)
Comment 4 Timur 2022-04-01 08:46:43 UTC
(In reply to QA Administrators from comment #3)
> it's possible that the bug has been fixed, or the details have changed. 
Is this an April joke? 
No change in 7.4+-