Support forums » Products » Cute Editor for .NET » Re: Bug with un-editable/selectable tags.

Bug with un-editable/selectable tags.

Last post 02-18-2005, 4:12 PM by yvesamyot. 5 replies.
Sort Posts: Previous Next

  •  12-06-2004, 1:11 PM 2865

    Bug with un-editable/selectable tags.

    Reply Quote

    We have noticed an issue with the un-editable/selectable tags. We noticed that when we have an area set and un-editable/selectable, you can still drag foreign objects into that section.

     

    eg. If I lock a td tag, we cannot click in it or type in it. But if we drag some text from another part of the page into that cell, it will work.

     

    Additionally, is there any way to prevent the changing of the locked sections in the HTML view?

  •  12-06-2004, 1:23 PM 2867 in reply to 2865

    Re: Bug with un-editable/selectable tags.

    Reply Quote

    This example shows that the UNSELECTABLE attribute is not inherited by child objects. Text in the TEXTAREA element can be selected and modified, but the text in the parent SPAN element cannot be selected. 

    <P>
<SPAN ID="oSpan" UNSELECTABLE="on" >This text cannot be selected.
<P>
<TEXTAREA WRAP="PHYSICAL" ROWS="5" STYLE="font-weight: bold;" ID="oTextarea">
This text can be selected and overwritten.
</TEXTAREA>
</P>
This text closes the SPAN and cannot be selected either.
</SPAN>
</P>

    For more information, please check:

  •  12-07-2004, 10:06 AM 2894 in reply to 2867

    Re: Bug with un-editable/selectable tags.

    Reply Quote
    Hi Adam,
     
    Your last reply doesn't solve the issue.  The issue is the following.  In Design View (WYSWYG), when you drag a portion of the page that is editable/selectable and drop it into a section that has been set to uneditable/unselectable it allows the content to be dropped into the non-editable regions.
     
    This breaks the concept of having regions that are uneditable/unselectable as you can add subchildren by dragging content into the uneditable areas.
     
    Let me know what your thoughts are on this issue...i'm not sure it will be an easy one to implement, but I think it is a very important feature as most CMS solutions will be using templates (which are set to unselectable/uneditable)... and it is useless if users can simply drag and drop content into template which is supposed to be off-limits.
     
    maybe a simple check can be performed which ensures that the parent container does not have uneditable=on defined...if it does...simply paste the content back where it came from...otherwise it is ok to drop it in the new location.
     
    Oh, also can you move this thread to the CuteEditor 4.0 area since that is where it belongs?

    Cheers,
     
    Eric

  •  12-07-2004, 2:04 PM 2902 in reply to 2894

    Re: Bug with un-editable/selectable tags.

    Reply Quote
    The issue is the following.  In Design View (WYSWYG), when you drag a portion of the page that is editable/selectable and drop it into a section that has been set to uneditable/unselectable it allows the content to be dropped into the non-editable regions.
     
    Eric,
     
    I don't think you can drop anything into a region which has been set as

    UNSELECTABLE="ON" contenteditable="false"
     
    Can you double check your code??

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  02-18-2005, 10:20 AM 4171 in reply to 2902

    Re: Bug with un-editable/selectable tags.

    Reply Quote
    We tried to use templates with some editable region.  It's sound great but we are not able to block the external region of the template.

    In technical word, all the content is content in a tag <div id="template" contenteditable="false"> ... </div>.
    And the part to edit are content in <div id="area1" contenteditable="true"> ... </div>.

    But, in the editor, the user can add content out of the main div named "template".
     
    How can we block this ?
     
     

  •  02-18-2005, 4:12 PM 4172 in reply to 4171

    Re: Bug with un-editable/selectable tags.

    Reply Quote
    Hi,

    I resolve the problem about contentEditable property set by default to True at the outside of the root node of code to be available in the editor.  You can see here the code needed to use full featured template approach.


    Add this code to your head node of the page where editor is define :

    <scriptlanguage="javascript">

    function
    beUneditable(){

        var editor1=document.getElementById('<%=Editor1.ClientID%>');

        var editdoc=editor1.GetDocument();

        editdoc.body.contentEditable =

    false;
    }
    </
    script>

    Add onload call in the body tag of the same page :

    <

    bodyonload="beUneditable()">
     
     
    Injoy!
View as RSS news feed in XML