I think I'm talking to myself, here...

But just in case anyone has run into this problem with cs5...

I usually create editable regions with content alone (minus divs).  It seems that cs5 won't allow this somehow.  I do this so that my clients won't move the div and can highlight the text that they want to change without screwing up the placement of the divs or having to click on it several times in Contribute in order to highlight the text.

Example: (This one works)

      <!-- TemplateBeginEditable name="LeftContent" -->
   <div id="contentLeft">
        <table width="100%" border="0" align="left" cellpadding="5" cellspacing="0" background="images/transBack.png">
        <tr><td>
          <h1>Heading Goes Here</h1>
          <p>Lorem ipsum eum erant soleat perfecto ex, ei pro mentitum aliquando theophrastus. Quodsi lucilius adolescens nec te, alia melius dissentias id eum, eu vel atqui munere eligendi. Eu eum viris suscipit, mei iracundia persequeris necessitatibus ad, qui putent vocent comprehensam ea. Eos sumo illud fuisset ea, sit doming dolorum fierent ea. Vis rebum aperiri nonummy at, ne eam impedit persequeris accommodare.</p>
          <p>An dico veritus evertitur cum, mentitum legendos theophrastus mei ei, qui hinc timeam honestatis ad. Ut illum takimata gloriatur eam, ei nullam propriae delicata vel, has ea solum ludus. Pro solum ridens inciderint ad, te ius vocent perfecto, partiendo scripserit reformidans cum te. No fastidii scaevola maiestatis mei, percipit praesent abhorreant eam no. Ea vim nobis dolore ignota, quodsi inciderint ei vel. Velit dicam te cum, te inermis principes percipitur per, animal constituam his an.</p>
          </td></tr>
          </table>
          </div>
      <!-- TemplateEndEditable -->

          (This one doesn't)

   <div id="contentLeft">

<!-- TemplateBeginEditable name="LeftContent" -->
        <table width="100%" border="0" align="left" cellpadding="5" cellspacing="0" background="images/transBack.png">
        <tr><td>
          <h1>Heading Goes Here</h1>
          <p>Lorem ipsum eum erant soleat perfecto ex, ei pro mentitum aliquando theophrastus. Quodsi lucilius adolescens nec te, alia melius dissentias id eum, eu vel atqui munere eligendi. Eu eum viris suscipit, mei iracundia persequeris necessitatibus ad, qui putent vocent comprehensam ea. Eos sumo illud fuisset ea, sit doming dolorum fierent ea. Vis rebum aperiri nonummy at, ne eam impedit persequeris accommodare.</p>
          <p>An dico veritus evertitur cum, mentitum legendos theophrastus mei ei, qui hinc timeam honestatis ad. Ut illum takimata gloriatur eam, ei nullam propriae delicata vel, has ea solum ludus. Pro solum ridens inciderint ad, te ius vocent perfecto, partiendo scripserit reformidans cum te. No fastidii scaevola maiestatis mei, percipit praesent abhorreant eam no. Ea vim nobis dolore ignota, quodsi inciderint ei vel. Velit dicam te cum, te inermis principes percipitur per, animal constituam his an.</p>
          </td></tr>
          </table>

<!-- TemplateEndEditable -->
          </div>

Anyone else have this?  Or even use this?
    

Message was edited by: JulesN

I still want the old way back because if I have my clients use Contribute, they can easily highlight the text.  If the div tag is selected in the template, then they have to click on the text several times to select it.  If you find out or if anyone out there has a suggestion... would love it!  I think I might report it to Adobe as a bug.

I think that I may be onto something!  I use css overflow:auto in a lot of my templates.  I discovered that the templates that didn't use that css didn't lock me out in design view, so just by chance, I commented out overflow:auto, and Bob's your Uncle!  It worked.  I have just been on the phone for an hour with Adobe, got off the phone and tried this out.  I still think it needs fixing, but at least it's working with a simple deactivation of a line of css.  Hopefully, this helps anyone else that builds their templates this way!!!

They have sent it in as an issue.  They were extremely happy that I phoned back to tell them what solved the problem. They agreed that a css statement should not cause an issue like that.  Hopefully it is something they can work out fast.  It's OK to have to do that, but it's certainly a pain in the arse!  LOL

Using CS5, they have a new feature that lets you disable the css temporarily.  Saves loads of time commenting out the css.  Find it in the CSS menu and just click on the left side of the overflow rule.  There will be a red circle with diagonal cross.  Sooo much easier than trying to comment out, especially if you have lots of css on one page or several pages of css.

Thought I'd let you know in case you didn't know about this new feature.