Services
Support
Store
©2015 Intersoft Solutions. All rights reserved.

User Profile & Activity

Michael Gardipee Member
Page
of 2
Misspelled inserted words, in an edittable IFrame, are not found by Spell Checker
Posted: December 21, 2010 10:54 AM

That's my mistake then. I downloaded the hotfix WebTextEditorNET1_0_1000_12.zip and only used the Text Editor assemblies as those were the only assemblies in the ZIP file. I'll update the WebUIFramework Assembly and see if that addresses the issue. What version is current?

 

Thanks,

Michael

Misspelled inserted words, in an edittable IFrame, are not found by Spell Checker
Posted: December 16, 2010 11:30 AM

Attached is a zip file of a project I created from one of our pages that has this issue. Lots of stuff commented out as you can see, but you should be able to see the issue.

 

Regards,

Michael

Misspelled inserted words, in an edittable IFrame, are not found by Spell Checker
Posted: December 14, 2010 9:41 PM

I understand. I should have something for you tomorrow. I have created a small application today that can reproduce it but have a few things left to do. I find that it fails about 90% of the time to find the misspelled word when its inserted and I am trying to figure out what makes it work that other 10% of the time.

 

Thanks,

Mike

Misspelled inserted words, in an edittable IFrame, are not found by Spell Checker
Posted: December 14, 2010 5:05 PM

As always, this is part of a larger application so I will have to try to build an example outside of our application that exhibits this behavior.


Thanks,

Mike

Using SpellChecker, with context menu and a standard ASP Text Box
Posted: September 14, 2010 8:51 AM

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

Using SpellChecker, with context menu and a standard ASP Text Box
Posted: September 13, 2010 2:12 PM

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

Using SpellChecker, with context menu and a standard ASP Text Box
Posted: September 8, 2010 11:25 AM

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.

 

When a misspelled word is preceded by a Period, Comma, Semi Colon or Parenthesis, the misspelled word is not identified by Spell Checker. I will create a defect to track this issue, but is this something that will be getting fixed?

　

             　　　　　　　　 Verify that a misspelled word proceeded by punctuation is identified:

　　　　　　　　 Verify that a misspelled word proceeded by punctuation is identified:

　　　　　　　　 Period - DEFECT

　　　　　　　　 Period - DEFECT

　　　　　　　　 Comma - DEFECT

　　　　　　　　 Comma - DEFECT

　　　　　　　　 Semi colon : - DEFECT

　　　　　　　　 Semi colon : - DEFECT

　　　　　　　　 Colon : - DEFECT

　　　　　　　　 Colon : - DEFECT

　　　　　　　　 Parenthesis " - DEFECT

　　　　　　　　 Parenthesis " - DEFECT

　　　　　　　　 Apostrophe ‘–PASS 4.5.5.4

　　　　　　　　 Apostrophe ‘–PASS 4.5.5.4

                                        　　　　　　　　 Left/Right () Bracket –PASS 4.5.5.4

　　　　　　　　 Left/Right () Bracket –PASS 4.5.5.4
Using SpellChecker, with context menu and a standard ASP Text Box
Posted: September 8, 2010 11:17 AM

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

 

Using SpellChecker, with context menu and a standard ASP Text Box
Posted: September 3, 2010 7:39 AM

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

Using SpellChecker, with context menu and a standard ASP Text Box
Posted: September 2, 2010 3:53 PM

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

 

 

All times are GMT -5. The time now is 3:30 AM.
Previous Next