MoveToAncestorNode does not return the correct node

[Henry Lyne]

This seems to be a problem in IE7 and Safari. FCK.Selection.MoveToAncestorNode does not return the correct node, or SelectNode doesn't properly select.

Steps to recreate:

1. Edit source and add

   <div><p><b>bbbbbbb</b><br /><i>iiiiiiiiiii</i></p></div>
   

   Switch back to the regular editor view.

2. Select "iiiiiiiiiii".

3. Run the following via the browser address bar:

    javascript: alert(frames[0].FCK.Selection.SelectNode( frames[0].FCK.Selection.MoveToAncestorNode('DIV') ));
    javascript: alert(frames[0].FCK.InsertHtml('abcd'));
   

4. View Source
   • IE7 has the following:

     <div><p><b>abcd</b><br />&nbsp;</p></div>
     

• Safari has:

  <div><p>abcd</p></div>
  

Output should look like:

abcd

[Martin Kou]

I'm not totally sure if this can be fixed. If you check the value returned by SelectNode() you'll find that it is indeed returning the <div> node.

SelectNode() isn't at fault here as well. IE's selection model does not allow you to select the <div> node itself - the reason is because it only uses caret positions to express a text selection. If you've used the DOMRange::selectNode() and DOMSelection.addRange() in Safari to select the the <div> node yourself, you'll notice document.execCommand('inserthtml' ...) will give you the same buggy result as us.

So the real culprit here is that the browser doesn't remember the selection correctly, and the symptom appears in FCK.InsertHtml() because InsertHtml() depends on the browser's view on where the selection is. If you happen to be writing a plugin to FCKeditor and want to replace entire block nodes, I recommend you to take a look at fckdomrange.js and use the FCKDomRange class in it instead.

[Artur Formella]

Replying to martinkou:

IE's selection model does not allow you to select the <div> node itself. (...)

So the real culprit here is that the browser doesn't remember the selection correctly, and the symptom appears in FCK.InsertHtml() because InsertHtml() depends on the browser's view on where the selection is.

[Frederico Caldeira Knabben]

There is actually a problem here. The fact is that the current implementation makes it hard to fix it. So this is a valid ticket.

We should investigate it more, and possibly close it as CantFix if we really find out that there is no other way for us with this.

[Piotrek Koszuliński]

There's no such a method like moveToAncestorNode and insertHtml has been completely rewritten, so I'm closing this issue as expired.