Jeremy Quinn wrote: > > On Wednesday, Jan 15, 2003, at 19:49 Europe/London, Jeremy Quinn wrote: > > > And it also fails to move compound elements, because the 'moveDotTo > > previousElement' moves to the last most inner child of the > > previousElement, not the previousElement itself (as the DOM API would > > define it). > > > > Is this a bug, or intended behaviour? (No offence intended) > >
The problem with XXE is that there are few bugs and many stupid intended behaviours :) > On further thought, I imagine you went to great effort to make it > happen this way ;) > > I guess it is the difference between a 'coder's DOM viewpoint' and an > 'editors page viewpoint'. > > ie. your paradigm is one of a word processor document, not a DOM. > > Maybe the solution to this could be to augment the moveDotTo command > with 'previousSibling' and 'nextSibling' which could act in more of a > DOM-type way. I think that command selectNode will do what you want (note that this command also moves the caret inside the selected node whenever possible and if the caret is not already inside the selected node). See http://www.xmlmind.com/xmleditor/_distrib/docs/poweruser/ar01s05s30.html
