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 15 years ago

Closed 15 years ago

#5424 closed Bug (fixed)

SCAYT takes a lot to activate

Reported by:	Frederico Caldeira Knabben	Owned by:
Priority:	Normal	Milestone:	CKEditor 3.3
Component:	UI : Spell Checker	Version:	SVN (CKEditor) - OLD
Keywords:	Confirmed	Cc:	WebSpellChecker.net

Description

At least on the current trunk, SCAYT is taking a lot of time to get enabled when activated. It just took me more than two minutes when enabling it with just a short phrase and two dispelled words.

The Firebug Net pane shows precisely that some spellckecker.net calls are having a quite long response time.

Change History (2)

comment:1 Changed 15 years ago by WebSpellChecker.net

Spellchecker.net hosting configuration updated: enabled gzip compression for JavaScript and HTML content, Keep-Alive parameters updated, cache-control parameters updated.

comment:2 Changed 15 years ago by Garry Yao

Resolution:	→ fixed
Status:	new → closed

The SCAYT initial time is much reduced after #5551, feel free to reopen the ticket on any further discoveries.

Note: See TracTickets for help on using tickets.

Download in other formats: