Bug 62777 - EDITING: When scaling down picture, Writer leaves empty gap under picture.
Summary: EDITING: When scaling down picture, Writer leaves empty gap under picture.
Status: RESOLVED DUPLICATE of bug 47355
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.0.2.1 rc
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-26 20:17 UTC by Zoran Vidaković
Modified: 2013-03-26 22:19 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Circle shows empty gap. (149.04 KB, image/jpeg)
2013-03-26 20:17 UTC, Zoran Vidaković
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Zoran Vidaković 2013-03-26 20:17:23 UTC
Created attachment 77077 [details]
Circle shows empty gap.

Problem description: 
When scaling down picture, Writer leaves empty gap under picture.

Steps to reproduce:
1. Type some text, at least two paragraphs
2. Insert fairly large picture in first one
3. Set anchor "As character" (it really doesn't matter)
4. Try to Shift-click and scale it down (it does the same thing even when I set picture options Width and Height manually in Picture dialog)

Current behavior:
When I do steps above, it leaves empty gap between bottom of picture and following text below picture.
I can remove it by clicking right side of picture, and then pressing "Delete" and then "Enter", but I don't think it should work like that.

Expected behavior:
When I scale down image, it should automatically fit all contents to it's place.

Note:
I'm using XUbuntu 12.10 and I experienced same thing on Crunchbang Waldorf. I don't know latest-known working version.
Operating System: Linux (Other)
Version: 4.0.2.1 rc
Comment 1 manj_k 2013-03-26 22:19:18 UTC
Thanks, already reported as 'Bug 47355 - [EDITING] When shrinking an object anchored as character, paragraph below it doesn't update its position'.

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