https://bugs.documentfoundation.org/show_bug.cgi?id=173088

--- Comment #2 from Matthias R. <[email protected]> ---
I saw the whiteboard was set to QA:needsComment. No specific question was
attached, so here is a retest with a result that narrows this report down
considerably.

Retested with 26.2.5.2 on Windows 11, then again after restarting in Safe Mode
(Help > Restart in Safe Mode, continue with profile and extensions temporarily
disabled), using a freshly generated four-page test document with misspellings
spread across pages.

On the scrolling part of this report: in Safe Mode the view does jump to the
page containing the next match, correctly. So that half is not a core Writer
problem, it comes from something in my own user profile or one of my
extensions. I'll narrow that down on my side and it should not be tracked here.
Apologies for putting it in the report in the first place.

On the highlight part: this reproduces in Safe Mode with a clean profile. When
the dialog moves to the next word, that word carries only the regular text
selection, which is drawn semi-transparent by default, and on a dense page of
body text it is easy to miss entirely. You end up reading the context snippet
in the dialog and hunting for the spot by eye. Before the Application Colors
page was folded into the theme system there was a Selection entry with a
Transparency checkbox that could be switched off to get a solid, clearly
readable highlight. I can't find any equivalent GUI control in the current
Appearance page.

So the remaining request is narrower than what I originally filed: while the
Spelling dialog is open, the word it is currently on should be visibly
distinguishable in the document, and there should be a way to control that
without hand-editing themes.xcu inside a theme extension.

Happy to adjust the summary to match, or to have this closed and refiled with
the correct scope if that is cleaner for QA. I can also attach a screencast of
the Safe Mode run if that helps with confirmation.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to