Bug 158642 - Dark mode: "Text boundaries" set to "automatic" obscure the cursor when line is empty
Summary: Dark mode: "Text boundaries" set to "automatic" obscure the cursor when line ...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.6.2.1 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Dark-Mode
  Show dependency treegraph
 
Reported: 2023-12-11 16:39 UTC by nvhorst
Modified: 2024-11-11 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
cursor invisible in empty lines (43.38 KB, application/vnd.oasis.opendocument.text)
2023-12-11 16:39 UTC, nvhorst
Details

Note You need to log in before you can comment on or make changes to this bug.
Description nvhorst 2023-12-11 16:39:01 UTC
Created attachment 191361 [details]
cursor invisible in empty lines

I have dark theme on my sytem.
I also have set:
Options > LibreOffice > Application colors > Custom colors > _A_utomatic to "dark" so to have inverted colors of a page.

In Options > LibreOffice  > Application colors > User interface elements the "Text boundaries" is SELECTED and set to "automatic"

In attached document I cant see the cursor when it is at the beginning of empty line. Pressing enter adds another line as expected, but the cursor is still invisible. It looks like it was obscured with text boundary.

Cursor though becomes visible if
1) "Text boundaries" is UNCHECKED OR
2) "Text boundaries" is set to any color other than "automatic" OR
3) Options > LibreOffie > Application colors > Custom colors > _A_utomatic is set to "light".

In general the bugs looks like the Text boundaries when set to automatic, covered blinking caret.
Comment 1 Dieter 2023-12-27 11:34:14 UTC
(In reply to nvhorst from comment #0)
> Created attachment 191361 [details]
> cursor invisible in empty lines
> 
> I have dark theme on my sytem.

What is your system? Please past information form Help -> About LibreOffice
Thank you

=> NEEDINFO
Comment 2 nvhorst 2023-12-27 13:39:16 UTC
Version: 7.6.2.1 (x86) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (pl_PL); UI: en-US
Comment 3 QA Administrators 2023-12-28 03:11:20 UTC Comment hidden (obsolete)
Comment 4 Stéphane Guillou (stragu) 2023-12-29 22:56:20 UTC
Not reproduced on:

Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Can you please share a screenshot of the issue?
Comment 5 John 2024-04-09 05:56:01 UTC
I was not able to reproduce this issue:

Version: 24.2.0.3 (X86_64) / LibreOffice Community
Build ID: da48488a73ddd66ea24cf16bbc4f7b9c08e9bea1
CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 6 QA Administrators 2024-10-10 03:13:31 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2024-11-11 03:13:28 UTC
Dear nvhorst,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp