Bug 115625 - FILEOPEN DOCX: Text Frame Placed on Wrong Position
Summary: FILEOPEN DOCX: Text Frame Placed on Wrong Position
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.6.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Textbox
  Show dependency tree / graph
 
Reported: 2018-02-11 06:26 UTC by Kevin Suo
Modified: 2019-01-13 19:11 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
test.docx (33.07 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-02-11 06:26 UTC, Kevin Suo 		Details
screenshot good (7.41 KB, image/png)
2018-02-11 06:27 UTC, Kevin Suo 		Details
screenshot bad (9.00 KB, image/png)
2018-02-11 06:27 UTC, Kevin Suo 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Suo 2018-02-11 06:26:13 UTC 
Created attachment 139768 [details]
test.docx

The attached sample DOCX file contains a text frame, and below the text frame is a table. If I open it with MSO 2010, the text frame appears above the table without intersection. However, when I open with LibreOffice, the text frame is "intersecting" with the table.

Steps to Reproduce:
1. Open the attached test DOCX file.

Expected Result:
See screenshot "good". This is the result when open with MSO 2010.

Current Result:
See screenshot "bad". this is the result when open with LibreOffice.

Version: 6.0.1.1
Build ID：60bfb1526849283ce2491346ed2aa51c465abfe6
CPU 线程：4; 操作系统：Linux 4.14; UI 渲染：默认; VCL: gtk2; 
区域语言：zh-CN (zh_CN.UTF-8); Calc: group
Fedora 27 x64.
Comment 1 Kevin Suo 2018-02-11 06:27:38 UTC 
Created attachment 139769 [details]
screenshot good
Comment 2 Kevin Suo 2018-02-11 06:27:59 UTC 
Created attachment 139770 [details]
screenshot bad
Comment 3 Kevin Suo 2018-02-11 07:21:44 UTC 
Bug already exists in: 5.4.0.0.alpha1+ 9feb7f7039a3b
Comment 4 Kevin Suo 2018-02-12 01:37:33 UTC 
Also exists in version 3.6.7.2. So it may never work.
Comment 5 IWAMOTO 2018-02-19 06:39:39 UTC 
This was reproduced in the following environment.


Version: 6.0.1.1 (x64)
Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6
Locale: ja-JP (ja_JP);
OS:Winsows7 Home Premium x64