The default focus in the dialog should provide a meaningful action if enter is pressed. The Ignore button would be one such. If you feel like another button/element should have the default focus, share your comments. You can find attached a sample that provides tabIndexes and default focus. This improvement is related to http://feedback.telerik.com/Project/108/Feedback/Details/126937
RadSpell's dialog should have proper tabIndex order to provide keyboard navigation. You can find attached a sample that lets you provide the desired order. When the buttons are disabled the browser should not focus them (i.e., the disabled attribute should prevent this even if tabIndexes are not modified). Related to this improvement request: http://feedback.telerik.com/Project/108/Feedback/Details/126935
Currently, only a few of the mistkaes are shown in the "Not In Dictionary" box. Once a word is changed or ignored, new ones are added. When the number increases, words from the beginning are removed. This property/method should let the spell control show all the text at once.
You can find more information about the problem, cause and repro in the following thread: http://www.telerik.com/community/forums/spell-check-hander-error-the-length-of-the-string-exceeds-the-value-set-on-the-maxjsonlength-property
RadSpell uses a RadWindow for its dialog which, in turn, uses RadFormDecorator. Thus, RadSpell should expose its RenderMode property in order to allow the developer to make the popups consistent on the page (i.e. avoid mixing modes which is not supported) and to avoid styling issues with the dialog. Currently the following web.config setting can be used to change the rendering mode of all RadWindows in the application, including the ones used by RadSpell: <add key="Telerik.Web.UI.Window.RenderMode" value="Lightweight" /> and this one for the RadFormDecorators: <add key="Telerik.Web.UI.FormDecorator.RenderMode" value="lightweight" />
The issue is preventing the users from adding a word to RadSpell custom dictionary. A workaround is attached. You can apply the DialogScriptFile property to all RadSpell instances through an ASP Theme. The bug will be fixed in Q1 2015 SP1, so as soon as you upgrade to this release (or a later one), you should remove the workaround.
I would like to have RadSpell should automatically check the words through the available dictionaries. If we attached two dictionaries to the editor / textbox, may be one word not found in English but the same word can be found in German. So it will be better to check both dictionaries before giving the suggestions. Thanks