There are two types of WebSpellChecker user interface.

Red-wave Underline Highlight

WebSpellChecker introduces more natural, intuitive way to perform spell checking with red wave highlight feature. To correct misspelled words, just click on each word and choose the correct word from the displayed context menu. It makes spell checking faster and easier than ever.

The red-wave highlight feature can only be enabled on editable IFRAME.

Sleek Dialog Box Interface

This mode will be automatically enabled when the target control is not an editable IFRAME. The dialog box interface includes visual elements that display checked words and the list of the suggested words. Just double-click on a word in suggestion list or click on the Change button to correct the misspelled word with the selected suggested word, and finally click on Done button to accept all changes and close the dialog box.

I have discussed about your specific scenario with WebSpellChecker development team. The team said that it is not possible to implement the red-wave highlight SpellChecker UI to an ASP.NET TextBox because there is no way to insert the red-wave highlight into an ASP.NET TextBox. The only element that can be inserted with the red-wave highlight is the editable IFRAME.

Hope this helps.

Thanks for the reply. That is what I figured, but I wanted to be sure. So, there are (2) defects that Intersoft is working on so that I can use the ASP Textbox approach and until those are resolved, I need to have a plan "B", so I will implement the Editable IFrame.

It seems that the Spell Checker is having problems with some characters and would like to know if you can replicate what I see. Try pasting what I have below into your editable IFrame and then spell check it. Hopefully you will see several script errors like I did...

I have attached a Word Document that shows what I see when I paste the above text into the IFrame running the Intersoft Sample application - not my application.

Thanks,

Michael Gardipee

Additionally, there is a bug with the spell checker that should be looked at.

If you type the following, noting the fact that there is no period at the end of the sentence, all mispelled words - including the last one - is picked up and underlined as expected.

Eror in the spell chec

Now, type that same sentence and add a period, like this

Eror in the spell chec.

You'll now find that the last word - chec - is not marked as being misspelled because the period is there, whereas without the period (above example), it is marked correctly.

That is the bug.

Thanks,

Michael Gardipee

It seems that the Spell Checker is having problems with some characters and would like to know if you can replicate what I see. Try pasting what I have below into your editable IFrame and then spell check it. Hopefully you will see several script errors like I did...

<ISWebTextEditor:WebSpellChecker ID="WebSpellChecker1" runat="server" Height="50px" Width="100px" TargetControlId="content" TargetControlIdValue="innerHTML" ContextMenuStyle="IntersoftStyle" DictionaryDirectory="/Dictionary/"> <ClientSideEvents OnAfterCheckSpell="OnAfterCheckSpell" OnBeforeCheckSpell="OnBeforeCheckSpell" OnContextMenu="OnContextMenu" OnInitialize="OnInitialize" OnClickContextMenuItem="OnClickContextMenuItem" OnExitSpellCheck="OnExitSpellCheck" OnReplaceWord="OnReplaceWord" /> </ISWebTextEditor:WebSpellChecker> 

I have attached a Word Document that shows what I see when I paste the above text into the IFrame running the Intersoft Sample application - not my application.

I have carefully followed the steps mentioned in the above quote and was unable to reproduce the issue in our local test.

Additionally, there isa bug with the spell checker that should be looked at.

If you type the following, noting the fact that there is no period at the end of the sentence, all mispelled words - including the last one - is picked up and underlined as expected.

Eror in the spell chec

Now, type that same sentence and add a period, like this

Eror in the spell chec.

You'll now find that the last word - chec - is not marked as being misspelled because the period is there, whereas without the period (above example), it is marked correctly.

That is the bug.

I was able to reproduce this issue on our local test. I have discussed this issue with WebTextEditor development team. They said that this issue happen because when the period is added into the last word (“chec”), WebSpellChecker considered that the period is a part of the “chec” word. When WebSpellChecker tries to compare it with the dictionary, there is no result that states if this word “cache.” is misspelled.

I have submitted this bug to WebTextEditor development team under work item #792. I’ll keep you updated with any news I heard from the team regarding this issue.

I am glad you can reproduce the second issue and hopefully it can be resolved soon. For the first issue that you cannot reproduce, I am a little surprised by that. I first saw the issue in my implementation of the Spell Checker so in an attempt to rule out something I may have been doing, I ran the "Live Samples" on my development machine that were installed when I installed WebStudio 2010 RC and got the exact same error. I then tried it on your website's live samples and could not reproduce it there because the text I pasted would always get replaced with the text that is there when the page is initially rendered.

With that said, is this a huge issue??? Not really as I am not expecting our users to paste things like that but it concerns me that there may be certain characters that are causing problems if the text is being treated as XML or the like.

So, based on the fact that this issue occurs in both my application and the "Live Samples" you should be able to reproduce it unless you're using different assemblies. Regardless, I am more interested in the bug related to the spell checker not catching the last word in a sentence.

Thanks,

Michael Gardipee

About the first issue, since you said that it is reproduce-able using the local-live sample, could you please kindly let us know the detail of step-by-step to replicate the issue?

I just got news from the WebSpellChecker development team that the issue related to the added period sign will cancel the spell check has been solved. I’m going to test the nightly-build of the hotfix before I send it to you. I’ll keep you updated with the test result.

Please do not click on autoreply. It seems you posted into "Intersoft Community Notification services".
However, I received your last post via email (forwarded from development division).

I already followed your step by step but still unable to replicate this issue.
It seems this error only showed in RC installer.
To get the latest assemblies, I suggest you to uninstall the RC and installed the release version.
http://www.intersoftpt.com/Community/ClientUI/Updated-WebUI-Studio-2010-Installer-Is-Now-Available/.
Hope this helps.

Regards,
Handy

Actually, our QA group has found that any word that is either preceded by or followed by the following (4) characters will cause the spell checker to miss words that are misspelled.

Semi Colon (;)

Colon (:)

Period (.)

Comma (,)

Thanks,

Michael Gardipee

Darn - I forgot (1) character. The same will happen with a parenthesis, either open or closed. Here is the actual note from our defect tracking system as posted by one of our QA members.

Hello,

I have been forwarded your replied regarding my last post.

I uninstalled the RC and installed R1, and have the same problem. This isn’t earth shattering for us as I alluded to in my postings, just that it exists and I am wondering if it is the tag structure that is throwing you off.

Would you mind to let us know about your environment details. We still could not replicate in here.
About your QA result, I will need to discuss with our developer teams about this issue.

Regards,
Handy

So it sounded like you have a fix for the punctuation that preceded or follows misspelled words. Is that something I can get and test out? Time is short for us so either we have to document that this is a known issue in our help system, or get it fixed.

Thanks,

Michael Gardipee

I’d like to inform you that WebTextEditor development team has managed to fix the issue (as submitted under work item #792). I also have ensure that the issue no longer persist using the nightly-build hotfix of WebTextEditor 1. I’ve uploaded the nightly-build hotfix to be tested on your end. Please let us know whether the nightly-build hotfix helps or not.

Please download the nightly-build hotfix of WebTextEditor at here.

Note

*The nightly-build hotfix has not been extensively tested (disclaimer on). So, we are really appreciate if you have encountered an issue can kindly give us a feedback of it.

*Please carefully follow the step-by-step shown in this link, in order to apply the hotfix manually.

*Please close all opened Microsoft Visual Studio opened project during applying the hotfix.

*After finish apply the hotfix to your development machine, please don’t forget to apply this hotfix to your own project.

*It is recommended to do ‘iisreset’; clear ‘Temporary ASP.NET Files’ in “C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files” folder; and clear browser’s cache before re-test the issue using the hotfix.

Good news related to this fix. The following has been resolved with the latest build:

Any misspelled word followed by one of the following is now underlined, and working correctly:

• Period
• Comma
• Semi Colon

There are still some open issues however.

Any misspelled word followed by any of the following is NOT underlined as misspelled

• Colon
• Parenthesis

Any misspelled word PRECEDED by any of the following is NOT underlined as misspelled.

• Period
• Semi Colon
• Colon
• Comma
• Parenthesis

So, we're getting closer but it's not complete. I appreciate that prompt response as our release candidate can not go to our clients until these issues are resolved.

Thanks,

Michael Gardipee

Thank you for the feedback regarding the nightly-build of the hotfix.
I have forwarded this to the development team to be fixed.

I’d like inform you about the status of work item #792.

WebGrid development team has managed to get the issue resolved in WebGrid 7. I have tested the nightly build of the hotfix and found that the issue no longer persists.

Should you need to have the nightly build hotfix to be tested on your local end, please let us know.