Created attachment 107341 [details] Comparison Textboxs in 4.4 vs 4.3 The margins of imported DOCX textboxes have been reduced and moved in 4.4. When a textbox is up against the margin, it's so bad that the text is outside of the box's border line. This issue occurs on the screen and when printed. Step to reproduce: 1) Create a new doc with a textbox in Word2007+ 2) Snap the textbox to the left margin 3) Save 4) Open in Write 4.4 This is a regression in 4.4. Libreoffice 4.3 sets the margins of imported textboxs correctly, so the imported textbox looks like Word's.
Created attachment 107342 [details] Simple DOCX file showing issue with reduced margins
confirmed under Win7x64 using 4.4.0.0.alpha0+ Build ID: 268b9c10c9ff27c74678ace99762f28d58d33012 TinderBox: Win-x86@42, Branch:master, Time: 2014-10-02_23:35:24 status NEW.works fine with 4.3.2.2 hence regression. issue is limited to .DOCX format, .DOC and .ODT are unaffected. @Luke please define the O/S where you reproduced the bug. moreover when you report bugs against master is always a good thing to copy and paste Build ID info from the "Help/About LibO dev" textbox
Within the daily dbgutil bibisect repo, from `git bisect good`: 49ffb467231cc09d9e351aa2d37f2c0d99c3eb3d is the first bad commit commit 49ffb467231cc09d9e351aa2d37f2c0d99c3eb3d Author: Miklos Vajna <vmiklos@collabora.co.uk> Date: Thu Jun 19 08:24:47 2014 +0200 2014-06-19 :100644 100644 426040151e25ab34608c1a48dcc8ce13f56cd591 7c0067294d629d902d426a1017494a199b13ddbe M build-info.txt :040000 040000 48d4cbc2d07d98d0855650a07a3591184041f373 a0503b6bedcbb741ca300660091d132f8cf56bf6 M opt and from `git bisect log`: # bad: [3bd90766c05c07c4a39e36cb1d3106b0016983d4] 2014-10-05 # good: [b3130c846de5cf1b4be48b48dfc780bb369549fa] 2014-05-21 git bisect start 'origin/master' 'oldest' # bad: [5ed7df78a02df9f716188ab12cc6f641f479b6d1] 2014-07-29 git bisect bad 5ed7df78a02df9f716188ab12cc6f641f479b6d1 # bad: [402ad27d59e542f8ff5fc88c4ffa74613a3cadfc] 2014-06-24 git bisect bad 402ad27d59e542f8ff5fc88c4ffa74613a3cadfc # good: [5507b65dd2f68bdc720e23686e57269d46c16411] 2014-06-07 git bisect good 5507b65dd2f68bdc720e23686e57269d46c16411 # good: [8415e4b7f11bc7defc143883e5daf89e90643de7] 2014-06-15 git bisect good 8415e4b7f11bc7defc143883e5daf89e90643de7 # bad: [49ffb467231cc09d9e351aa2d37f2c0d99c3eb3d] 2014-06-19 git bisect bad 49ffb467231cc09d9e351aa2d37f2c0d99c3eb3d # good: [35c0f684cef2fdbe270ff9d3b37169731ef61033] 2014-06-17 git bisect good 35c0f684cef2fdbe270ff9d3b37169731ef61033 # good: [2d5ec4b381617f69c8daf3f149f71425af0ce9e9] 2014-06-18 git bisect good 2d5ec4b381617f69c8daf3f149f71425af0ce9e9 # first bad commit: [49ffb467231cc09d9e351aa2d37f2c0d99c3eb3d] 2014-06-19
It's obviously a regression from d379d18666aa42031359ca8eb34b0021960347ae, I plan to look into this.
(This is an automated message.) Setting priority to highest as this is a MAB. This is part of an effort to make the importance of MAB reflected in priority too.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.