Thank you for your response Alan. I am working on a windows platform and the version of spellerchecker I am using is

Infragistics2.WebUI.WebSpellChecker.v11.1, Version=11.1.20111.2178, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb

Thank you

Hello Akwasi,

Please explain in more details the issue you're encountering while using the spellchecker. Does it behave inappropriate when you attempt to check the spelling or does some issue occur while you're loading the page? Are any exceptions or other errors being thrown?

In the meantime I've created for you a sample using service release 11.1.20111.2178 which demonstrates user control that hosts WebSpellChecker, TextBox and Button controls inside of it. Please take a look at the attached sample and feel free to modify it and reproduce the issue according your settings. If you have any further questions, please let me know.

Sincerely,

Tsanna

Thank you Tsanna,

My issues is I have aspx page that calls selected custom controls which comprises of one or two textboxes and date pickers etc. I added  spell checker to the ascx page to check spelling for all the text boxes in the selected custom control. Anytime the check spelling button is clicked, instead of opening spell checker dialog, it brings up the aspx page is a new window. I tried fixed the issue by created spell checker control with the textbox and a button. It works when I put it in a aspx page but I need it in the ascx page. Can I call a control in another control? Any help will be deeply appreciated.

Thank you,

Akwasi

Hello Akwasi,

I am still following  your case. Have you been able to resolve the issue? If you need more assistance please let me know.

Thank you for choosing Infragistics components!

Sincerely,

Tsanna

Hi Tsanna,

Thank you for following up on this issue. I may have to explain my issue better. I am trying to use the spell checker in my custom user control which has some textboxes and date fields. I want to apply the spell check on each of the textboxes in the custom user control I have created. What I have tried so far that seems not to be working is using the spell check directly in the .ascx page, so I am using the spell check for each textbox in the user control, this didn't work. Also I created a stand alone spell check control comprising of a textbox and a button but that doesn't work either when I place it in the custom user control I created initially. Hope you understand what I am trying to do and can help.

Thank you

Hello Akwasi,

Thank you for your patience.

Apologies for the delayed response. I’ve created for you a sample that demonstrates custom user control which has some textboxes, button and a spell checker. The spell check is applied on each of the text box controls, however you should note that there is a known issue regarding similar scenario of multiple check in the latest service release for 13.1 (the sample was created using 12.2 build 2054) Therefore I've opened a private case for you with number: CAS-117511-S8N8C3 and have linked the development issue to it so that you'll be notified once the issue has been resolved.

You can find the case by going to your account on our web site and then to the "Support activity" tab. You can view the status of the development issue connected to that case by selecting the "Development Issues" tab when viewing this case.  Please let me know if you need more information.

Sincerely,

Tsanna

Hi Tsanna,

Thank you for the solution. It really did help, however, I still encountered some problems. The solution works without a masterpage but when a masterpage is added it throw a javascript error object not found. Please help me resolve this issue.

Thank you

Hello Akwasi,

Apologies for the delayed answer.

I’ve tested this scenario and it really throws a javascript error saying “object not defined”. Note that using a custom user control inside of master page,  places the WebSpellChecker inside of naming container. Therefore the UniqueID property value and the CliendID property value are generated by combining the ID values of all controls in the nesting hierarchy. By default the CliendIDMode property is set to “Predictable”, which means that the ClientID value is generated by concatenating the CliendID value of the parent naming container with the ID value of the control(including master page prefix in this case).  And using the following:  oWebSpellChecker1.checkSpelling($get(controls[currentIndex]).value, onTextChecked); will throw a javascript error as the mentioned at the beginning, because the CliendID reference is not correct. However if the ClientIDMode of the WebSpellChecker is set to “Static”, the ID values of controls that are higher in the hierarchy are not included. In this case the WebSpellChecker control will work with the following ClientID: oWebSpellChecker1.

Attached is a sample for your reference. If you have any further questions, please let me know.

Sincerely,

Tsanna