0006270: Native spell checking does not activate when replying to emails in Chrome until focus is manually changed - SOGo | BTS

ID	Project	Category	View Status	Date Submitted	Last Update

0006270	SOGo	Web Mail	public	2026-11-12 08:22	2026-11-12 08:22

Reporter	pschmidt	Assigned To
Priority	normal	Severity	tweak	Reproducibility	always
Status	new	Resolution	open
Platform	[Client] Microsoft	OS	Windows	OS Version	8
Product Version	5.12.11

Summary	0006270: Native spell checking does not activate when replying to emails in Chrome until focus is manually changed
Description	Native browser spell checking works correctly when composing a new email but does not activate when replying to an existing message. The issue occurs with both plain-text and HTML messages. Interestingly, moving keyboard focus away from the message editor and then back immediately activates spell checking.
Steps To Reproduce	Open SOGo Webmail in Google Chrome. Ensure native browser spell checking is enabled, with Polish selected. Compose a new email and type deliberately misspelled words. Chrome correctly underlines them. Close the composer and open an existing email. Click Reply. Type deliberately misspelled words in the reply editor. No spelling errors are underlined. Press Shift+Tab to move focus away from the editor. Press Tab to return focus to the editor. Actual result: Spell checking is initially inactive in the reply editor. It starts working immediately after a real keyboard-driven focus change. Expected result: Native browser spell checking should work immediately when replying, just as it does when composing a new message
Additional Information	The editor uses CKEditor 5. The editable element has contenteditable="true", spellcheck="true" and lang="pl". The Chrome spell-checking context menu shows Polish as enabled. Native spell checking works in standalone textarea and contenteditable elements on the same page. Programmatically calling blur() followed by focus() does not activate spell checking. A real keyboard focus transition (Shift+Tab followed by Tab) consistently activates it. Explicitly setting lang="pl" and toggling the spellcheck attribute does not resolve the issue. Possible cause The issue may be related to the initial focus handling or timing of CKEditor initialization when opening the reply composer. This is a hypothesis, not a confirmed root cause. Workaround: Press Shift+Tab followed by Tab after opening the reply composer. Native spell checking then works normally. Additional information: The issue is reproducible without custom JavaScript modifications to SOGo.
Tags	No tags attached.

Date Modified	Username	Field	Change
2026-11-12 08:22	pschmidt	New Issue