Bug 135109 - end of line blinking cursor placement
Summary: end of line blinking cursor placement
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.6.2 release
Hardware: All Windows (All)
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-24 17:06 UTC by Will
Modified: 2020-11-09 13:59 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Will 2020-07-24 17:06:26 UTC 
Description:
The blinking cursor at the end of line is inside the last character.  I notice it on every line.
It is especially noticeable
1. with a quote mark - cursor is between the two ticks
2. with a highlight extending to the end of line - last character is only partially highlighted.

Win10, 1903, build 18362.900
LibreOffice 6.3.6.2

Actual Results:
cursor at end of line is within the last character, not after it

Expected Results:
blinking cursor at end of line should be after the last character and not within the last character


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 Dieter 2020-11-09 07:05:05 UTC 
I can't confirm it with

Version: 7.0.3.1 (x64)
Build ID: d7547858d014d4cf69878db179d326fc3483e082
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: threaded

Does in also happen in SafeMode (Help => Restart in SafeMode)?

If this is the case, please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version. Change to RESOLVED WORKSFORME, if the problem went away.


=> NEEDINFO
Comment 2 Will 2020-11-09 12:19:42 UTC 
Currently using 6.4.6.2 and this issue is gone.  Thanks.