Bug 105940 - An image within a selection isn't really selected when it's anchored to page, so cut and paste isn't working
Summary: An image within a selection isn't really selected when it's anchored to page,...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 74231 88736 105939 (view as bug list)
Depends on:
Blocks: Writer-Images
  Show dependency treegraph
 
Reported: 2017-02-11 15:25 UTC by Telesto
Modified: 2023-11-20 20:32 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (682.65 KB, application/vnd.oasis.opendocument.text)
2017-02-11 15:26 UTC, Telesto
Details
Example file to paragraph (682.71 KB, application/vnd.oasis.opendocument.text)
2017-02-11 15:39 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2017-02-11 15:25:24 UTC
Description:
An image within a selection isn't cut a when it's anchored to page (and can't be pasted)

Steps to Reproduce:
1. Open attached file
2. Press CTRL+A
3. Press CTRL+X (image isn't affected)
4. Paste everything in a new document (image is missing)

Actual Results:  
Image isn't cut nor pasted


Expected Results:
Image should be selected, removed when cut, and pasted into the new document


Reproducible: Always

User Profile Reset: No

Additional Info:
Found in
Version: 5.4.0.0.alpha0+
Build ID: a296a69c984b17cfbcd249cf6bdc191d08dff2a6
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-02-06_00:00:55
Locale: nl-NL (nl_NL); Calc: group

and in
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4


User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Comment 1 Telesto 2017-02-11 15:26:05 UTC
Created attachment 131104 [details]
Example file
Comment 2 Telesto 2017-02-11 15:39:09 UTC
Created attachment 131105 [details]
Example file to paragraph

Seems also to be happening when set to paragraph in when certain conditions are met
Comment 3 Jean-Baptiste Faure 2017-02-11 17:10:07 UTC
*** Bug 105939 has been marked as a duplicate of this bug. ***
Comment 4 Xisco Faulí 2017-02-12 11:21:49 UTC
COnfirmed in

Version: 5.4.0.0.alpha0+
Build ID: a25b1ff25a3be97d688d66b12353b4217fd239a5
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group
Comment 5 QA Administrators 2018-02-13 03:32:55 UTC Comment hidden (obsolete)
Comment 6 Timur 2019-02-18 16:19:49 UTC Comment hidden (obsolete)
Comment 7 sdc.blanco 2020-01-31 13:54:31 UTC
Tested and repro "to page" anchor case

Version: 7.0.0.0.alpha0+ (x64)
Build ID: eeb2d19e77d6dc47c68e8ba0920a02cf64a1247b (22 jan 2020)
Comment 8 Mike Kaganski 2021-12-17 14:12:23 UTC
(In reply to Xisco Faulí from comment #4)
> COnfirmed

But what is confirmed?

The object's anchor (not its position!) is what defines what outer stuff should be selected to also select the object. When your object is anchored to character, you select the place of anchor, and that selects the object for the copy purposes. For paragraph-anchored objects, that's the same: you select start of the paragraph, and the object gets selected.

For page-anchored objects, there's no text flow that holds the object; hence it's normal and expected that no matter what text you select (even all the text using Ctrl+A), the object will not be copied as part of the selection. By the way, Ctrl+A doesn't copy other things in the document - which is just normal: say, unused user-defined styles don't go to the target document.

I suppose to close it NOTABUG. To page anchoring is very special, and actually a power user feature.
Comment 9 Stéphane Guillou (stragu) 2023-11-20 20:30:05 UTC
*** Bug 88736 has been marked as a duplicate of this bug. ***
Comment 10 Stéphane Guillou (stragu) 2023-11-20 20:32:31 UTC
*** Bug 74231 has been marked as a duplicate of this bug. ***