Bugs :
K-Meleon Web Browser Forum
If a link is clicked to an anchor near the bottom of a large HTML page, the page is opened at a random point, nearer the top of the page. Once the new HTML page is in cache, clicking 'back' and then the same link again, the anchor is found and page correctly displayed. So it would seem that this could be a timing issue, whereby the position in the new page is sometimes determined prior to the page being completely loaded.
One example in my website is a jump to line 510 in a 668-line HTML page. The incorrect point in the page displayed is around line 400.
(www.necon.co.za/megatruk.htm > installation notes > 'back' > installation notes)
The same incorrrect point is displayed whether accessing the local server over the LAN or the ISP over a slow ADSL link.
This problem is repeatable. I have noted similar issues on other web sites, so the problem has fairly widespread effects. This same problem also affects Firefox
If Firefox has the same problems it means that it can be a GRE problem.
The URL to start.
Moves to this place/anchor.
It might be a also site design problem.
Here You can also test.
For me, it works here.
I remember that it was hard to make the page load exact points.
Or the speed problem as You suggested, my page has less content and is at htp network / like me.
Edited 1 time(s). Last edit at 12/28/2008 11:29AM by guenter.
This is a bad designed web. Anchor situation is correct but this changed when images are loaded. This is because in web source code you can see that images aren't size defined (high and width properties in <img> tags).
K-Meleon in Spanish
I have observed that many times. It always happens in pages that are sloppily made with a ton of images; any very heavy page, really. I have assumed that it is not possible to go to a certain part of a page until that part is loaded -- the data must reach my computer first, through that tiny wire in the wall, it is not magic. To ask a browser to read what it does not yet have is asking the impossible. So I wait. Or leave the stupid site.
A.K.A. Arual the Wyrd
You can talk about issues with k-meleon here.
Links to anchors in long HTML pages
Posted by:
NeilF
Date: December 28, 2008 08:09AM
If a link is clicked to an anchor near the bottom of a large HTML page, the page is opened at a random point, nearer the top of the page. Once the new HTML page is in cache, clicking 'back' and then the same link again, the anchor is found and page correctly displayed. So it would seem that this could be a timing issue, whereby the position in the new page is sometimes determined prior to the page being completely loaded.
One example in my website is a jump to line 510 in a 668-line HTML page. The incorrect point in the page displayed is around line 400.
(www.necon.co.za/megatruk.htm > installation notes > 'back' > installation notes)
The same incorrrect point is displayed whether accessing the local server over the LAN or the ISP over a slow ADSL link.
This problem is repeatable. I have noted similar issues on other web sites, so the problem has fairly widespread effects. This same problem also affects Firefox
Re: Links to anchors in long HTML pages
Posted by:
guenter
Date: December 28, 2008 11:26AM
If Firefox has the same problems it means that it can be a GRE problem.
The URL to start.
Moves to this place/anchor.
It might be a also site design problem.
Here You can also test.
For me, it works here.
I remember that it was hard to make the page load exact points.
Or the speed problem as You suggested, my page has less content and is at htp network / like me.
Edited 1 time(s). Last edit at 12/28/2008 11:29AM by guenter.
Re: Links to anchors in long HTML pages
Posted by:
desga2
Date: December 28, 2008 04:23PM
This is a bad designed web. Anchor situation is correct but this changed when images are loaded. This is because in web source code you can see that images aren't size defined (high and width properties in <img> tags).
K-Meleon in SpanishRe: Links to anchors in long HTML pages
Posted by:
Matera the Mad
Date: January 02, 2009 03:39AM
I have observed that many times. It always happens in pages that are sloppily made with a ton of images; any very heavy page, really. I have assumed that it is not possible to go to a certain part of a page until that part is loaded -- the data must reach my computer first, through that tiny wire in the wall, it is not magic. To ask a browser to read what it does not yet have is asking the impossible. So I wait. Or leave the stupid site.
A.K.A. Arual the Wyrd
English