pullo — 2011-06-28T07:10:07-04:00 — #1
When I open the following link in IE, Opera, Safari or Chrome, it works as it should. The content which follows the anchor tag (<a name="neuro">) in the source code, is displayed at the top of the viewport.
However, when I open the same link in Firefox 4 or Firefox 5, the browser jumps straight to the bottom of the page, not to the anchor tag.
I've looked at the source code of the above page and the anchor seems to be specified correctly. There is only this one anchor element with a name of "neuro" and there are no other tags on the page with this name, id or class.
Does anyone have a clue as to why FF4 and FF5 are doing this?
FF3 worked as it should.
Thanks in advance.
xhtmlcoder — 2011-06-28T07:33:09-04:00 — #2
It works correctly for me albeit you do have a lot of markup errors in that page and it would have been preferable to use ID rather than the name attribute. Did you mean to place a 'fragment identifier' for the actual h3 rather than above the mp4?
pullo — 2011-06-28T07:48:50-04:00 — #3
It's not my page dude. I just want to link to it.
It's full of markup errors and the code is horrible - no question, but I can't do anything about that.
But do I understand correctly, that when you click on the above link in FF4 or FF5, the window that opens looks like the image below?
xhtmlcoder — 2011-06-28T14:42:11-04:00 — #4
Yes, that is where it is supposed to link to according to the markup and that's where Fx does take me when I click on the above link (I land at same place as seen in that JPG).
pullo — 2011-06-28T16:00:27-04:00 — #5
Sorry to be persistent, but which Firefox version are you using?
I have tried FF4 at work and FF4 + 5 at home on multiple computers and when I click on the above link I see what's in the jpeg below.
This is the bottom of the page.
Could anyone else with Firefox 4 or 5 try this out for me?
zcorpan — 2011-06-29T04:18:17-04:00 — #6
Works for me with Nightly on mac. But you could file a bug anyway. I suspect it could have to do with the page being rendered without styles the first time, then Firefox jumps to the anchor, then the styles are applied and Firefox doesn't update the scroll position, or something (I saw a flash of unstyled content first time but the scroll position was correct anyway).
pullo — 2011-06-29T09:04:38-04:00 — #7
Thanks for the replies.
Could anyone else confirm if they are seeing the same thing in FF4 or FF5 (i.e. the bottom of the page instead of the anchor) and if they think it is a bug.
ralphm — 2011-06-29T09:09:23-04:00 — #8
Yeah, I see the bottom of the screen in FF4 PC.
pullo — 2011-06-29T09:17:44-04:00 — #9
Cheers Ralph, do you think this is a bug?
If so, how does one go about reporting it?
ralphm — 2011-06-29T09:41:19-04:00 — #10
Normally such links work fine in FF4 and presumably 5 (I just did a test to convince myself) so I'd say it's something to do with the bad coding of that page, as others have suggested.
xhtmlcoder — 2011-06-29T09:49:33-04:00 — #11
Well, it seems to be fifty-fifty at the moment; it worked for me and Simon but not for yourself and Ralph.
zcorpan — 2011-06-29T09:56:00-04:00 — #12
Sure, but it should still work. File a bug here https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CCore
pullo — 2011-06-29T10:01:42-04:00 — #13
As Simon is on a Mac, it might be a PC thing.
This is getting interesting.
Robert, are you on a PC or a Mac? Which FF version are you using?
xhtmlcoder — 2011-06-29T10:21:49-04:00 — #14
pullo — 2011-06-29T10:42:33-04:00 — #15
I filed a bug as Simon suggested.
Let's see what happens.
Thanks for the help so far.
pullo — 2011-06-30T16:29:11-04:00 — #16
Just a quick update:
The guys over at Bugzilla seem to agree that this is undesired behaviour on FF's part. I don't know what kind of importance they will give to fixing this, but it is good to know that it is not something wrong with the original web page.
Someone also pointed out that in about:config, setting "html5.parser.enable" to "false", makes this go away.
Could this be the reason that you are seeing correct behaviour Robert?
zcorpan — 2011-07-01T03:52:55-04:00 — #17
What's the bug number?
pullo — 2011-07-01T03:58:43-04:00 — #18
xhtmlcoder — 2011-07-01T07:08:29-04:00 — #19
I have html5.parser.enable as true I don't alter the config as a general rule. Although I typically surf without JS but I doubt that would alter the results.
paulob — 2011-07-01T07:50:27-04:00 — #20
The problem in the site linked to seems to be caused by this strange tag in the head combined with the imported css files.
<imp:live-info sysid="2517d20c-54d1-18b6-6e03-c6f99a666cba" node_id="/1/849" />
If that line is removed then the page works correctly.
next page →