Bug 135624

Summary:	Content detached from frame after undo
Product:	LibreOffice	Reporter:	Telesto <telesto>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	xiscofauli
Priority:	medium	Keywords:	bibisected, bisected, regression
Version:	6.4.0.3 release
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=135623
Whiteboard:
Crash report or crash signature:		Regression By:
Attachments:	Example file

Description Telesto 2020-08-10 21:10:13 UTC

Description:
Content detached from frame after undo

Steps to Reproduce:
1. Open the attached file
2. Select the frame
3. CTRL+X
4. CTRL+V
5. Place cursor below the existing frame and paste again
6. Move the secondly paste frame to a different position
7. Press Undo

Actual Results:
Top frame loses position

Expected Results:
Frame and content should stay together


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: <buildversion>
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: ru-RU (nl_NL); UI: en-US
Calc: CL

not in 6.3 (which does have the flaw in a different form after total undo followed by full redo)

Comment 1 Telesto 2020-08-10 21:10:28 UTC

Created attachment 164139 [details]
Example file

Comment 2 Telesto 2020-08-10 21:11:32 UTC

Also in
Version: 6.4.0.0.beta1+ (x64)
Build ID: 20be5cd0bdc57d812bf34a2debfe48caa51de881
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CLb

Comment 3 Xisco Faulí 2020-08-11 08:48:29 UTC

Reproduced in

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

Comment 4 Xisco Faulí 2020-08-13 15:25:14 UTC

Regression introduced by https://cgit.freedesktop.org/libreoffice/core/commit/?id=09228fabe88f3457105cf26d83c003719a793114
Closing as a duplicate of bug 133490

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