Hello,

Since we only target Internet Explorer, I suspect we only need the Style part of the fix and not the script part? Assuming this is correct (which seems to work) this doesn't entirely satisfy my requirement.

I need the automatic colouring and underlining to be prevented when in HTML view, but not in Design View. As far as I can see, the suggested fix 'corrects' the automatic styling in both views.

Is there a way to only apply the style to the HTML preview element and no the Design view element? As far as i could tell, these were using the same htmlEditor_tw element.

Alternatively, is there a way to know which view is currently being shown and modify the css style accordingly?

Thanks

Hi,

Thank you steps. Now I undertood what you refer to. Similar "friendly" replacement of text by link-object is used in almost all Microsoft products/editors and I am in doubt that is possible to disable that feature using public properties.
Building of that object happens not by typing actual text of address, but by typing Space or Enter at the end of that text. So, existing text can be converted to "link-object" by Space. That "build-object" functionality can be toggled by obscure combinations of BackSpace/Space characters at the end of address-text.

To get around, I do not recommend to use css classes, but to process keypress-with-delay or keyup events, check for A object(s) and remove it(them).
The underlined text may appear for awhile and disappear. I hope that end-users may live with that. In that respect the keypress is preferrable, because end-user may press and hold Space key and the A object will stay until end-user releases key. Below is example to implement.

<script type="text/javascript">
 function WebHtmlEditor1_KeyPress(oEditor)
 {
  if (oEditor._html && oEditor._ie) setTimeout(function()
  {
   var div = oEditor._elem;
   if (div.getElementsByTagName('A').length > 0)
    div.innerHTML = div.innerText;
  }, 5);
 }
</script>

<ighedit:WebHtmlEditor ID="WebHtmlEditor1" runat="server" ...>
   <ClientSideEvents KeyPress="WebHtmlEditor1_KeyPress" />
</ighedit:WebHtmlEditor>

Hi,

You are correct. When I tested last my codes, then I tried only space/backspace keys and only one line of content. I forgot that Enter key is not processed by keypress event and that innerText might not work well, if explicit new lines are created within HTML view.

I replaced keypress by keydown and replaced over-simplified innerText by fixing real DOM objects (which is what I intended to do before).

I also added "speed-up" condition to process only low keys. You may replace
keyCode < 33
by something like
(keyCode == 32 || keyCode == 13)
or if autoformat will happen with other keys, then corresponding keyCodes can be added to that condition.

<script type="text/javascript">
 function WebHtmlEditor1_KeyDown(oEditor, keyCode)
 {
  if (oEditor._html && oEditor._ie && keyCode < 33) setTimeout(function()
  {
   var elems = oEditor._elem.getElementsByTagName('A'), i = elems.length;
   while (i-- > 0)
   {
    var a = elems[i];
    a.parentNode.replaceChild(document.createTextNode(a.innerHTML), a);
   }
  }, 5);
 }
</script>

<ighedit:WebHtmlEditor ID="WebHtmlEditor1" runat="server" ImageDirectory="~/images/htmleditor/">
 <ClientSideEvents KeyDown="WebHtmlEditor1_KeyDown" />
</ighedit:WebHtmlEditor>

Hi,

In the first scenario you could you could use innerText instead of innerHTML in Victor’s code, in order to prevent the encoding of characters:

function WebHtmlEditor1_KeyDown(oEditor, keyCode, oEvent) {

    if (oEditor._html && oEditor._ie && keyCode < 33) setTimeout(function () {

        var elems = oEditor._elem.getElementsByTagName('A'), i = elems.length;

        while (i-- > 0) {

            var a = elems[i];

            a.parentNode.replaceChild(document.createTextNode(a.innerText), a);

        }

    }, 5);

}

And here is a possible workaround for the second case you described:

document.onclick  = function () {

    var elems = iged_getById("WebHtmlEditor1")._elem.getElementsByTagName('A'), i = elems.length;

    while (i-- > 0) {

        var a = elems[i];

        a.parentNode.replaceChild(document.createTextNode(a.innerText), a);

    }

}

This should prevent the auto-styling in these particular scenarios.

If you have any further questions, please do not hesitate to ask.

Hi Warwick,

If you find any other issues with this matter, please let me know.

Hi,

Thanks for the replies. The latest workarounds still had an issue when clicking outside the control if on the design view. I added similar code to first workaround, ie: oEditor._html && oEditor._ie and it seemed to work correctly.

This still needs to go through our QA process but hopefully everything will be fine.

Thanks.

Hello Warwick,

Please let me know if you have any other concerns.