We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Ticket
Next Ticket →

Opened 14 years ago

Closed 14 years ago

#5864 closed Bug (duplicate)

config.disableNativeSpellChecker = true not working in Google Chrome

Reported by:	Erik Kangas	Owned by:
Priority:	Normal	Milestone:
Component:	General	Version:	3.3.1
Keywords:		Cc:

Description

The same CKEditor settings viewed in Chrome and FireFox 3.6. Chrome displays red underlines for misspelled words and FireFox does not. When SCAYT is enabled, we see double underlines in Chrome on words that both SCAYT and Chrome believe are misspelled.

Change History (1)

comment:1 Changed 14 years ago by Frederico Caldeira Knabben

Resolution:	→ duplicate
Status:	new → closed

DUP of #1314.

Note: See TracTickets for help on using tickets.

Download in other formats: