Version: (using KDE Devel) Installed from: Compiled sources OS: Linux KHTMLPart::gotoAnchor does not go to anchor if the html text has been set with write() method. There is a simplish application in http://iki.fi/eelik/khtmlbug.tar.bz2 which can be used to reproduce the bug. The relevant code is basically similar to this: m_part->begin(); m_part->write(htmlText); m_part->end(); m_part->gotoAnchor(anchorString); I put some debugging statements in the kde code. The result (with one specific html text) is this: ************************************************************ testi(25799)/khtml (part) KHTMLPart::gotoAnchor: start testi(25799)/khtml (part) KHTMLPart::gotoAnchor: x: 0 , y: 0 testi(25799)/khtml (part) KHTMLPart::gotoAnchor: will call a->getUpperLeftCorner(x, y); testi(25799) DOM::NodeBaseImpl::getUpperLeftCorner: start testi(25799) DOM::NodeBaseImpl::getUpperLeftCorner: will call o->container()->absolutePosition testi(25799) khtml::RenderBox::absolutePosition: this: "RenderInline(2): 0x8456acc {0 0} il ci nl rmm zI: auto anchor <a> (0,0,0,0) [-1--1] { mT: 0 qT: 0 mB: 0 qB: 0}" testi(25799) khtml::RenderBox::absolutePosition: will call container (RenderObject) ->absolutePosition testi(25799) khtml::RenderBox::absolutePosition: this: "RenderInline(2): 0x8456a68 {0 0} il ci nl rmm zI: auto <span> (0,0,0,0) [-1--1] { mT: 0 qT: 0 mB: 0 qB: 0}" testi(25799) khtml::RenderBox::absolutePosition: will call container (RenderObject) ->absolutePosition testi(25799) khtml::RenderBox::absolutePosition: this: "RenderInline(2): 0x8456a04 {0 0} il ci nl rmm zI: auto <div> (0,0,0,0) [-1--1] { mT: 0 qT: 0 mB: 0 qB: 0}" testi(25799) khtml::RenderBox::absolutePosition: will call container (RenderObject) ->absolutePosition testi(25799) khtml::RenderBox::absolutePosition: this: "RenderBlock(34): 0x82aeb78 {0 0} ci nl rmm zI: auto <div> (0,-500000,0,0) [-1--1] { mT: 0 qT: 0 mB: 0 qB: 0}" testi(25799) khtml::RenderBox::absolutePosition: will call container (RenderObject) ->absolutePosition testi(25799) khtml::RenderBox::absolutePosition: this: "RenderBody(1): 0x82aeaf4 {0 0} nl rmm zI: auto <body> (0,-500000,0,0) [-1--1] { mT: 0 qT: 0 mB: 0 qB: 0}" testi(25799) khtml::RenderBox::absolutePosition: will call container (RenderObject) ->absolutePosition testi(25799) khtml::RenderBox::absolutePosition: this: "RenderBlock(1): 0x82aea0c {0 0} nl rmm <html> (0,-500000,0,0) [-1--1] { mT: 0 qT: 0 mB: 0 qB: 0} layer=0x82aea90" testi(25799) khtml::RenderBox::absolutePosition: will call container (RenderObject) ->absolutePosition testi(25799) khtml::RenderCanvas::absolutePosition: start testi(25799) khtml::RenderBox::absolutePosition: 0x82aea0c will return true, xPos: 0 , yPos: -500000 testi(25799) khtml::RenderBox::absolutePosition: 0x82aeaf4 will return true, xPos: 0 , yPos: -1000000 testi(25799) khtml::RenderBox::absolutePosition: 0x82aeb78 will return true, xPos: 0 , yPos: -1500000 testi(25799) khtml::RenderBox::absolutePosition: 0x8456a04 will return true, xPos: 0 , yPos: -1500000 testi(25799) khtml::RenderBox::absolutePosition: 0x8456a68 will return true, xPos: 0 , yPos: -1500000 testi(25799) khtml::RenderBox::absolutePosition: 0x8456acc will return true, xPos: 0 , yPos: -1500000 testi(25799)/khtml (part) KHTMLPart::gotoAnchor: x: 0 , y: -1500000 testi(25799)/khtml (part) KHTMLPart::gotoAnchor: 6 testi(25799)/khtml (part) KHTMLPart::gotoAnchor: gox: -10 testi(25799)/khtml (part) KHTMLPart::gotoAnchor: KHTMLPart::gotoAnchor: going to setContentsPos, gox: -10 , y: -1500000 ************************************************************ This shows that RenderBox absolutePosition returns a wrong value. The value should have been updated somewhere but it's not. Therefore it is -500000 which is a default value set in some phase with setPos().
Build against KHTML 4.2.91 and qt 4.5 it doesnt even open the html page
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!