Version: (using KDE 4.4.0) OS: Linux Installed from: Mandriva RPMs This started to happen somewhere in 4.4 release cycle so for me it is 4.4. vs. 4.3 regression. I have a link that contains an anchor (i.e. should point inside of referred page). Very often Konqueror position window with such URL not on anchor but usually somewhere below; exact amount of shift varies. This is becoming to really hurt at times as example below shows. I attach three screenshots. First is original page (http://lwn.net/Articles/372935/) which contains article "Development project priorities"; below as usual is link to comments. I open comments in new window (tab). Instead of being shown the first comment I am shown some one or two below (see second screen shot). Next one is even worse. In the above comments there is a link to mailing list archive (http://mailman.videolan.org/pipermail/vlc-devel/2009-September/thread.html#66426) which refers to specific message. Third screen shot demonstrates what I get opening it (new tab again). Instead of being positioned at messages #66426 I am thrown st bottom of the page without any practical way to easily locate message I wanted to see.
Created attachment 40948 [details] Initial LWN page showin link to comments
Created attachment 40949 [details] LWN page with comments after opening using previous link
Created attachment 40950 [details] Mialman link opened from previous page and completely misplaced
You can usually workaround by pressing enter in the location bar again, IIRC
Problem is still present in 4.8.3, but this seems to be a duplicate of bug 196520.
Still not fixed in 4.7.4. To me it's not a duplicate of bug 196520 as it happens not specifically on local files but in general, whenever anchors exists. It did not reported it sooner because I thought it too obvious not to be fixed ASAP. But it stills there.
(In reply to comment #6) > Still not fixed in 4.7.4. To me it's not a duplicate of bug 196520 as it > happens not specifically on local files but in general, whenever anchors > exists. > > It did not reported it sooner because I thought it too obvious not to be > fixed ASAP. But it stills there. It is a duplicate of 196520. There is nothing in that bug report that stated that the issue is limited to local files. *** This bug has been marked as a duplicate of bug 196520 ***