Boman.Biz

This one is not particularly exciting, but it might help someone wanting confirmation.  It seems that SharePoint 2010 still has a few bugs that need to be fixed and my colleague Adrian actually found this one:

On any SharePoint 2010 site:

1. Create a new Custom List
2. Add a Multi-Line Text Box field
   1. Set type to “Rich Text (Bold, italics, text alignment, hyperlinks)”
   2. Set Required to true.
3. Create a new item
4. Don’t put any data in and press save

The validators fire for title and the new field but also there is a JavaScript bug:

Invalid argument on Line: 2 Char: 141544 in sp.ui.rte.js

or if you have debug switched on:

Invalid argument on Line 7353 in sp.ui.rte.debug.js

This is still a problem after the December 2010 CU.

*** PROCEED WITH THE FOLLOWING AT YOUR OWN RISK ***

If you need an interim fix then we need to fix the offending JavaScript, and doing this breaks my SharePoint Golden Rule No. 6 – Never Modify the OOB files.  However if you need to do it then you might do something like this:

1. Navigate to your LAYOUTS folder, usually at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS
2. Make a copy of SP.UI.Rte.debug.js and SP.UI.Rte.js to restore for later when this is fixed in an update. (Restore your vanilla copy before running any subsequent CU’s or Service Packs)
3. Edit the SP.UI.Rte.debug.js around line 7353 …. from this:
   

   parentElement: function() {ULSkay:;
       var $v_0 = this.$8;
       if ($v_0.parentElement) {
           var $v_2 = $v_0.parentElement();
           var $v_3 = RTE.DomHelper.createRange(window.document);
           if ($v_2) {
               $v_3.moveToElementText($v_2);
           }
           while ($v_2 && !$v_3.inRange($v_0)) {
               $v_2 = $v_2.parentNode;
               try {
                   $v_3.moveToElementText($v_2);
               }
               catch ($$e_3_0) {
               }
           }
   
   

   To look like this:
   

   parentElement: function () {
           ULSkay: ;
           var $v_0 = this.$8;
           if ($v_0.parentElement) {
               var $v_2 = $v_0.parentElement();
               var $v_3 = RTE.DomHelper.createRange(window.document);
               if ($v_2) {
                   try {
                       $v_3.moveToElementText($v_2);
                   } catch (gonk) {
                       //Do Nothing - SharePoint Bug.
                   }
               }
               while ($v_2 && !$v_3.inRange($v_0)) {
                   $v_2 = $v_2.parentNode;
                   try {
                       $v_3.moveToElementText($v_2);
                   }
                   catch ($$e_3_0) {
                   }
   

4. Save your changes and copy SP.UI.Rte.debug.js over the top of SP.UI.Rte.js – remembering that you have backups of both of these files to restore before applying future updates.

When testing this, make sure you clear your browser cache.

I really hope they fix this before or in SP1!

UPDATE: Have started a thread on MSDN to see if gets any bites: http://social.technet.microsoft.com/Forums/en-US/sharepoint2010programming/thread/50df5a23-c7c5-4e8b-859f-2a86ef137eb2/