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 Warwick,

I do not remember if I've ever seen underlined or any other formated text in HMTL view. Therefore, I assumed that you do not want to see link-style in Design view.

Can you provide steps or content of editor, which can be used to reproduce underlined text in HTML view?

There is no public method, which returns current view. Application may process client event AfterAction and check for ChangeView or it may use internal variable _html.

Example to process event:
function WebHtmlEditor1_AfterAction(oEditor, actID, oEvent, p4)
{
 if (actID == 'ChangeView')
  alert('HTML view:' + p4);
}

Example to get view (skipping validation for null)
var isHtmlView = iged_getById('WebHtmlEditor1')._html;

Note: I am not sure how easy it will be to add/remove css-class/style-sheet dynamically under IE. It handles stylesheets very different from all other browsers.

Hello,

This is what was requested in the initial post. I need to have the auto-styling in Design view and not in HTML view.

This has been reproduced by the support team and is being addressed by the Development team. I'll update this post when i get a response.

Thanks

Hi Warwick,

Thank you for clarification.
I was confused by statement about clickable links. Currently links, which appear in editable-DIV of IE, are not "clickable": at least browser does not do any actions.
I missed that your original question for #1 was about HTML view, because I did not see similar issue before and I assumed that question was about Design view.

I think, that the only scenario, when html objects (not text) may appear in HTML view, is when end user explicitly inserts objects using clipboard operations like copy/paste. In this case browser will perform requested operation and it will insert not only <a> objects, but everything what was copied: buttons, text fields, images, tables, etc. Those objects will appear in WebHtmlEditor (does not matter which HTML or Design view) not as strings, but as actual browser objects, which are created by browser from clip-board content. WebHtmlEditor does not interact with default functionality of browser related to copy/paste and is not able to modify that neither.

If that is the case with your question, then application may try to process paste event and disable or modify action of browser. It is quite easy to cancel paste. Checking and changing content of clipboard is probably possible as well, though, similar custom functionality is beyond features of WebHtmlEditor.

Example to process and cancel paste action when editor is in HTML view:

<script type="text/javascript">
 function WebHtmlEditor1_Initialize(oEditor)
 {
  oEditor._addLsnr(oEditor._elem, "paste", function(evt)
  {
   if(oEditor._html)
    iged_cancelEvt(evt);
  });
 }
</script>

<ighedit:WebHtmlEditor ...>
 ...
 <ClientSideEvents Initialize="WebHtmlEditor1_Initialize" />
</ighedit:WebHtmlEditor>     

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.

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.