| This may seems strange to you at first, but today I | | | | get prompted for spelling in these controls, let alone |
| got an email from our support engineer that reads: | | | | try and fix them! |
| Hi, | | | | So, after searching MS documentation with no luck |
| When doing spell checking on a list form with the | | | | (big surprise eh?), I came across one lone blog post |
| cascading field type, we are getting this error: | | | | that speaks of the SharePoint spell check feature, |
| Please assist | | | | and specifically how to register a control to be |
| Well... I know what you were thinking... this guy has | | | | excluded from spell checking. |
| some serious spelling mistakes, right? | | | | Turned out to be a rather simple task, all you need |
| Thing is, this text wasn’t actually a user input | | | | to do is add excludeFromSpellCheck=”true” |
| text – it was a hidden text box. You see, for | | | | to any input control you don’t want checked and |
| debugging purposes we sometimes use textboxes | | | | you are done! |
| with style=”display:none” instead of input | | | | P.S. funny thing is that the SharePoint people picker |
| type:”hidden” fields. | | | | field control also gets spell checked, prompting users |
| While SharePoint Spell Check skips hidden inputs, it | | | | on their domain name or user names... |
| does not skip hidden text boxes, so our textbox | | | | Maybe there will be a fix for that someday as well... |
| gets the same treatment as all other user inputs on | | | | For now – at least we can update our field |
| the page. | | | | controls and other web parts accordingly. |
| In our Cascading Lookup Plus Field Type we use | | | | Good luck and happy SharePointing! |
| hidden inputs like that to store information between | | | | Shai. |
| post backs. We believe it is important that users not | | | | |