Bug 135905 - Move caret at the end on dropping below the last position
Summary: Move caret at the end on dropping below the last position
Status: NEW
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:
Depends on:
Blocks: Text-Cursor
  Show dependency treegraph
 
Reported: 2020-08-19 08:21 UTC by Telesto
Modified: 2023-05-01 04:54 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (8.61 KB, application/vnd.oasis.opendocument.text)
2020-08-19 08:21 UTC, Telesto
Details
Screencast (5.60 MB, video/mp4)
2020-08-19 08:23 UTC, Telesto
Details
Screencast (254.48 KB, video/mp4)
2021-04-19 15:42 UTC, Telesto
Details
Screencast MSO (88.08 KB, video/mp4)
2021-04-19 15:44 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-08-19 08:21:11 UTC
Description:
Drag and drop incidentally pasted at end of the line (unknown trigger, only screencast) 

Steps to Reproduce:
1. Open the attached file
2. Look at the screencast.. try to reproduce (I'm not seeing the pattern)

Actual Results:
Once is a while is goes wrong.. 

Expected Results:
Should always work as expected


Reproducible: Sometimes


User Profile Reset: No



Additional Info:
Screencast taken with
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: nl-NL (nl_NL); UI: en-US
Calc: CL

Build of yesterday
Comment 1 Telesto 2020-08-19 08:21:34 UTC
Created attachment 164443 [details]
Example file
Comment 2 Telesto 2020-08-19 08:23:54 UTC
Created attachment 164444 [details]
Screencast

The first 2 minutes can be skipped.. but shows it's not that easy (I'm missing a step)
Comment 3 Dieter 2021-03-22 07:26:21 UTC
Telesto, unfortunately nothing has happened with this bug report for more than half year. So I'd like to ask, if it is still valid. Could you please try to reproduce it with the latest version of LibreOffice?
=> NEEDINFO
Comment 4 Telesto 2021-04-18 08:15:30 UTC
New steps.
1. Open attached file
2. Double left click around
3. Drag it down to void space
4. Release

Around moves to end of the text. 
Expected jumps back to original position. 

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: a809b2ab2553e946431699d9d7ac3f6209cbdd6b
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 5 Telesto 2021-04-18 08:17:44 UTC
Also in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

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


Adding UX-advise for more insights..
Comment 6 Heiko Tietze 2021-04-19 15:19:27 UTC
If you drag beyond the end, which is the fact when pulling down, it should drop at the end regardless the horizontal position. You wouldn't have become confused however when the caret goes to the right place at the end.
Comment 7 Telesto 2021-04-19 15:42:58 UTC
Created attachment 171291 [details]
Screencast
Comment 8 Telesto 2021-04-19 15:44:36 UTC
Created attachment 171292 [details]
Screencast MSO
Comment 9 Heiko Tietze 2021-04-19 16:18:15 UTC
Do you suggest that we block dropping below the end of document (which places the dragged content at the end)?
Comment 10 Telesto 2021-04-19 17:15:22 UTC
(In reply to Heiko Tietze from comment #9)
> Do you suggest that we block dropping below the end of document (which
> places the dragged content at the end)?

That's kind of what I'm suggesting :P. There are so much where this this works. You really need to drag it to the 'empty space'. If there is (empty) paragraph below, this doesn't work at all.. 

So scope already limited. And well drag 'down' to empty space to put it at the end is not a really natural experience either. 

This is more bad drag accident drag in my perception. 

But if this is 'introduced' by design, then there is likely someone somewhere actually using finding. Else it's more a 'bug' which might be seen as feature by some?

I see it as a bug. Minor or trivial, but still a bug  if you ask me (with my current knowledge). But well hoping there more people in UX able to give some feedback.

Maybe this being useful in tables or something like that?
Comment 11 Heiko Tietze 2021-04-30 07:34:29 UTC
We discussed the topic in the design meeting. While I sympathize with the idea to block moving content beyond the end of the document it's understood as often-used convenience feature. So what we recommend is to keep the current status but put the caret at the last character to give a proper feedback.
Comment 12 QA Administrators 2023-05-01 03:18:47 UTC
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug