Bug 135285 - drag-and-drop mangles
Summary: drag-and-drop mangles
Status: RESOLVED DUPLICATE of bug 132892
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.0.1 rc
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-29 17:53 UTC by TorrAB
Modified: 2020-12-08 06:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
text to edit (13.42 KB, application/vnd.oasis.opendocument.text)
2020-07-29 17:55 UTC, TorrAB
Details
text to edit (13.06 KB, application/vnd.oasis.opendocument.text)
2020-07-29 17:57 UTC, TorrAB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description TorrAB 2020-07-29 17:53:56 UTC
Description:
	In Draga.odt, select ‘Tmax=Tp’ and drag it in front of ‘Tmin’: weird result!
	But if you hit ^x and copy it (^v) in front of ‘Tmin’, OK.
	Do the same with Drag.odt, and get another, different, bad result!


Steps to Reproduce:
1.see above
2.
3.

Actual Results:
Copy is mangled

Expected Results:
good copy


Reproducible: Always


User Profile Reset: No



Additional Info:
none
Comment 1 TorrAB 2020-07-29 17:55:59 UTC
Created attachment 163743 [details]
text to edit
Comment 2 TorrAB 2020-07-29 17:57:24 UTC
Created attachment 163744 [details]
text to edit
Comment 3 Telesto 2020-07-30 17:33:07 UTC
Confirm: expect it to be bug 132892
Comment 4 Buovjaga 2020-12-07 17:59:33 UTC
As bug 132892 has been fixed by reverting a commit, can you re-test?
Comment 5 TorrAB 2020-12-08 02:52:08 UTC
(In reply to Buovjaga from comment #4)
> As bug 132892 has been fixed by reverting a commit, can you re-test?

bug gone from
Version: 7.1.0.0.beta1 (x64)
Build ID: 828a45a14a0b954e0e539f5a9a10ca31c81d8f53
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-CA (en_US); UI: en-US
Calc: threaded

TY!
Comment 6 Buovjaga 2020-12-08 06:27:38 UTC
Thanks, let's dupe to the other one

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