Using FCKEditor 2.3.2 and IE 6.0, I have just enabled spell checking using SpellerPages / Aspell. The main functionality works great, however, I am getting a strange error message.
When you click to run the spell checker and only when there are no misspelled words, after clicking OK in the "Spell checking complete: no misspellings found" dialog, the spell checker window closes as expected but then a new warning dialog opens that says:
"It was not possible to open the dialog window. Make sure all popup blockers are disabled"
All popup blockers are disabled and I'm not expecting any more dialog windows.
Again, the main spell checking functionality works fine, I'm just getting this annoying popup every time this scenario happens.
Any thoughts on what could be causing this or how to fix it?
Thanks,
Rob
When you click to run the spell checker and only when there are no misspelled words, after clicking OK in the "Spell checking complete: no misspellings found" dialog, the spell checker window closes as expected but then a new warning dialog opens that says:
"It was not possible to open the dialog window. Make sure all popup blockers are disabled"
All popup blockers are disabled and I'm not expecting any more dialog windows.
Again, the main spell checking functionality works fine, I'm just getting this annoying popup every time this scenario happens.
Any thoughts on what could be causing this or how to fix it?
Thanks,
Rob
RE: Strange Popup
In fckdialog.html, the loadInnerDialog() method calls window.setTimeout() and passes as argument an anonymous function that sets the window.returnValue to 'true'. When I clicked on the spell checker toolbar button the call to that function was only being executed the first time I opened the spell checker. Subsequent attempts never called the anonymous function and therefore the window's returnValue attribute was never defined.
The caller of all generic dialog windows, including the spell checker, checks the window's return value attempting to determine if a popup blocker has interfered. If the return value is undefined or false then it assumes the window did not open and shows the error message from this thread's initial post.
As a fix, I added a line of code at the beginning of the loadInnerDialog() method to set the returnValue attribute to true. By this time, the window has opened so the popup blocking mechanism should continue to work as designed.
Most likely, this issue has something to do with caching. I happen to be using FCKEditor within an Oracle Portal 10.1.4 environment so there are several layers of caching. Regardless, this update appears to be working well without having to manipulate my caching components.