Bug 119895

#4  0x4204a5e3 in Node (this=0xbfecb620, other=@0x38) at dom_node.cpp:141
#5  0x423a175c in DOMListViewItem::node (this=0x0) at domlistviewitem.h:48
#6  0x4239d0f1 in DOMTreeView::moveToParent (this=0x875a778)
    at domtreeview.cpp:728
#7  0x423a07e5 in DOMTreeView::qt_invoke (this=0x875a778, _id=52, 
    _o=0xbfecb6d8) at domtreeview.moc:240
#8  0x40d101f9 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#9  0x40d106a0 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40534565 in KAction::activated (this=0x87839c0) at kaction.moc:176
#11 0x405353b1 in KAction::slotActivated (this=0x87839c0) at kaction.cpp:1102
#12 0x4053471c in KAction::slotButtonClicked (this=0x87839c0, state=LeftButton)
    at kaction.cpp:1147
#13 0x405389b5 in KAction::qt_invoke (this=0x87839c0, _id=17, _o=0xbfecb824)
    at kaction.moc:220
#14 0x40d101f9 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x4060108d in KToolBarButton::buttonClicked (this=0x87aa548, t0=-83, 
    t1=LeftButton) at ktoolbarbutton.moc:154
#16 0x406012ff in KToolBarButton::mouseReleaseEvent (this=0x87aa548, 
    e=0xbfecbd24) at ktoolbarbutton.cpp:479

Taking. I didn't know people actually *use* the dom tree viewer ;-)

Actually, the tree viewer is *really* cool - mostly because it's also a tree editor.

Lots of sites rely on client-side security.

Accepting a license or other agreements becomes much more pleasant when I can edit the terms myself ;) (Nobody says that's forbidden... Or if someone does, the DOM tree viewer can fix that, too.)

But the DOM tree viewer does have some other bugs:
1) Repaint errors when moving/deleting nodes
2) "Delete" key is tied to two actions - both of them delete the node, but typing "Delete" brings up a popup-menu, asking to select the action.
3) Crashes when moving nodes in DOM::Node::insertBefore ()) - I'll see if I can figure out what's happening.
4) When moving nodes deep inside the tree, all open nodes that are about 7 levels deep automatically close (so the tree goes back to its original state)

These should probably be filed separately, though...

Glad you like it :-)

Concerning your bugs: If (1) occurs within the domtreeviewer window, it is new to me and should be filed. If it occurs within the konqueror window (i. e. the webpage itself), it is not a domtreeviewer bug and should be filed against konqueror/khtml rendering.

I know already about (2) and don't have the slightest idea on how to fix it. 

(3) should be reported if you have a reliable way to reproduce it. 

Last but not least, (4) sounds like a usability issue. If you can come up with a good procedure (step-by-step description) that shows how it works and how it is supposed to work, put it in a bugreport of its own and stress that it's a usability bug.

SVN commit 780505 by pino:

Do not crash when there is not an item selected, and asking to go to its parent.
(Usually happens on an empty tree.)

CCBUG: 119895


 M  +3 -1      domtreeview.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=780505

SVN commit 780513 by pino:

Restrict the two Delete actions to their widgets, so they do not conflict.

CCBUG: 119895


 M  +1 -20     domtreeview.cpp  
 M  +4 -0      domtreewindow.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=780513

The issue cannot be reproduced in trunk (rev. 793966).

Konqueror doesn't crash anymore when deleting the HTML from DOM tree viewer then clicking on the "up" button.

Confirmed for 3.5.9. Clicking the up-button twice after removing the HTML node still crashes konqueror.

is this bug still valid under kde 4 ?

This is fixed in KDE4 indeed. Other issues should be reported separately.