Firstly: the only one that drops the cookies is IE, the client code doesn't tell it: drop those cookies and keep these ones.
Second: I would file a ticket so that the cookies generated by the spellchecker don't include the path of the page, it seems more logical that such cookies are unique in a server, or at least that it's an option.
Third: be careful about the custom dictionary if you are already having issues with cookies:
Initially the User Dictionary is stored in a Cookie. However, Cookies are limited in size. When the User Dictionary grows to a point where it cannot be stored in a Cookie, then the dictionary may be stored on our server. To store your personal dictionary on our server you should specify a name for your dictionary. If you already have a stored dictionary, please type it's name and click the Restore button.
And I know that this won't help you, but you could suggest your users to switch to a different browser in the meanwhile. At least I hope that they aren't using IE6.
Yeah, sorry I didnt clarify that, but yes I am aware that this is an IE only issue. Unfortunately, the client requires this in IE since 99% of their 1000+ users use either IE6, 7 or 8. And yeah, I said IE6. Believe me, that is one of the largest points of contention at the moment, but that isn't really the major issue right now.
I filed a ticket, so thanks for that suggestion... Not sure how "actively" they monitor these tickets, but hopefully someone will see it and agree that its a legit issue.
We aren't dealing with the user dictionary at this time, but I will file it away as another potential issue down the road...
The SCAYT code is provided by spellchecker.net and usually any related change is done by them. You don't have any option to change this code, it seems to be located at the core libraries that are loaded from their servers at runtime. Fortunately, they usually take care of all their bugs and provide fixes, but as it happens with every company, it depends on what's their current schedule and plans.
So by posting a bug on the dev board for ckeditor, will that also get pushed through to them or do I need to post this as a bug on their support site as well?
Re: SCAYT cookies and MVC
Second: I would file a ticket so that the cookies generated by the spellchecker don't include the path of the page, it seems more logical that such cookies are unique in a server, or at least that it's an option.
Third: be careful about the custom dictionary if you are already having issues with cookies:
And I know that this won't help you, but you could suggest your users to switch to a different browser in the meanwhile. At least I hope that they aren't using IE6.
Re: SCAYT cookies and MVC
I filed a ticket, so thanks for that suggestion... Not sure how "actively" they monitor these tickets, but hopefully someone will see it and agree that its a legit issue.
We aren't dealing with the user dictionary at this time, but I will file it away as another potential issue down the road...
Re: SCAYT cookies and MVC
Re: SCAYT cookies and MVC
http://dev.ckeditor.com/ticket/7275
Re: SCAYT cookies and MVC
Fortunately, they usually take care of all their bugs and provide fixes, but as it happens with every company, it depends on what's their current schedule and plans.
Re: SCAYT cookies and MVC