[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-bugs-dist
Subject: [Bug 87486] New: Navigation to a #section of (new?) page requires
From: alan () chandlerfamily ! org ! uk
Date: 2004-08-19 7:23:49
Message-ID: 20040819072349.10203.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.kde.org/show_bug.cgi?id=87486
Summary: Navigation to a #section of (new?) page requires two
attempts to get there
Product: konqueror
Version: 3.3
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: konq-bugs kde org
ReportedBy: alan chandlerfamily org uk
Version: 3.3 (using KDE 3.3.0, (3.1))
Compiler: gcc version 3.3.4 (Debian 1:3.3.4-7)
OS: Linux (i686) release 2.6.7-1-k7
When calling up a URL with a #section at the end, it often seems to be the case (I \
think possibly when going to a new page rather than within the current) that the \
first attempt just navigates to the top of the page rather than to the correct \
section. If I hit the "back" button and try to link again it normally works.
I have noticed this particularly with the apache2 manual, where all the directives \
are organised by module with # sections for each directive.
For example, the following URL
http://httpd.apache.org/docs-2.0/mod/core.html#virtualhost
Will often navigate to the top of this page rather than to the virtualhost directive \
at the above section, when called from a page which is not the same URL
I have suspected that this could be a timing thing - related to whether the page was \
fully loaded at the time the navigation attempt was displayed - but I haven't found a \
way of proving or disproving this theory.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic