Version: 3.1.0 (using KDE KDE 3.0.99) Installed from: Debian testing/unstable Packages OS: Linux When displaying a fragment in the browser window after a redirection the browser window seems to be set as to where the fragment occured prior to CSS styling. For instance: http://goatee.net/smack the browser window is too high.
Sorry, I don't understand.. the page looks fine here, just like in Mozilla. What do you mean by "the browser window is too high."?
Subject: Re: Problems with dereferencing and displaying fragment identifiers On Saturday 17 May 2003 11:02, Daniel Naber wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=52671 I mean that when you dereference a URI with a fragment id, the browser viewport [1] is supposed to be set to the location of the fragment. This frequently doesn't happen in Konqueror. For example, if you dereference: http://goatee.net/smack The URL is rewritten to: http://goatee.net/2002/06#_13th and on the FIRST such dereferencing you are looking at the TOP of the page, not the appropriate fragment. On a subsequent dereferencing the veiwport is moved to the appropriate location. This bug does NOT require a redirect to be effected, it's just a convenient example. I also find that when I first dereference a web page with CSS that significantly changes the layout (floating a sidebar up to one side), again, the viewport is in the wrong place. Once it seems to have it in the cache, or a refresh it's taken to the correct fragment. [1] http://www.w3.org/TR/CSS2/visuren.html#q2
dup of bug 52608
Subject: Re: Problems with dereferencing and displaying fragment identifiers On Saturday 14 June 2003 10:20, kl@3dots.de wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > http://bugs.kde.org/show_bug.cgi?id=52671 > ------- Additional Comments From kl@3dots.de 2003-06-14 16:20 ------- > dup of bug 52608 Since 52608 is marked a dup as well, it'd be better perhaps to reference: http://bugs.kde.org/show_bug.cgi?id=57360 to which I will move my votes.
*** This bug has been marked as a duplicate of 57360 ***