Check out the following URL in Mozilla 1.2 nightly:
http://www.macvillage.net/news/
Then try it in IE, Opera, or some other browser
There should be an ad at the very top...
but it doesn't seem to appear (at least on my system) with Mozilla 1.2 nighty.
Anyone have an idea?
I have not seen this issue in any other browser.
iframe problem? Javascript?
-
- Posts: 282
- Joined: November 8th, 2002, 8:12 am
- Location: NJ
- Contact:
-
- Posts: 3
- Joined: November 27th, 2002, 10:44 am
Big problem
I think this has a wider impact than was realised and it really should have been fixed for 1.2. So far I've seen it myself on a couple of sites already, and on something I was working on. Mozilla 1.2 is not suitable for my daily use with this bug, and I won't be sending an email out recommending people upgrade to it (which I was planning to do). :/
Something is very wrong with how the DOM is being built. The main place I've noticed it is with iframes (mainly advert ones) that are just a link containing an image - the image does not render (if you look at the DOM it just isn't there!). I've also seen it lose style attributes. People have posted in the Mozilla Builds forum about seeing it with javascript generated pages.
After some testing, I believe this bug is triggered when you do not have <html> and/or <body> tags. Of course any compliant HTML page should have these, but as we all know, many do not! Pages designed to be contained in iframes, and javascript generated pages are the places where these are most frequently forgotten, and so where this bug is biting.
Something is very wrong with how the DOM is being built. The main place I've noticed it is with iframes (mainly advert ones) that are just a link containing an image - the image does not render (if you look at the DOM it just isn't there!). I've also seen it lose style attributes. People have posted in the Mozilla Builds forum about seeing it with javascript generated pages.
After some testing, I believe this bug is triggered when you do not have <html> and/or <body> tags. Of course any compliant HTML page should have these, but as we all know, many do not! Pages designed to be contained in iframes, and javascript generated pages are the places where these are most frequently forgotten, and so where this bug is biting.
- Rick Bull
- Posts: 76
- Joined: November 10th, 2002, 12:31 pm
- Location: England
- Contact:
-
- Posts: 3
- Joined: November 27th, 2002, 10:44 am
Rick Bull wrote:But I think (from memory) if you are using HTML 4 then HTML and BODY are not mandatory, but the browser should "add" them itself.
It normally does yes, but whether it's strictly correct according to the standards ... I didn't think so. I went to check though, and you're right. The open and close tags of the <html>, <head>, and <body> elements are all optional. However, a document type declaration is of course needed, and interestingly, exactly one <title> element is *required* per document. You learn something new every day. :) However, good practice says that one should always use <html>, <head>, and <body> elements - this makes your intent clear to both the browser, and to people viewing your code (yourself included).
Either way, it doesn't alter the fact that this is a bug. Whether or not that code is OK by the standards, Mozilla should be rendering it. Not just because other browsers do, and people expect it to, but because it does in every other release.
My main point before was that adding those tags is what appears to fix this bug (from my limited testing) - I hope that helps people.
- jgraham
- Posts: 558
- Joined: November 28th, 2002, 10:20 am
- Location: Cambridge, UK
- Contact:
-
- Posts: 630
- Joined: November 4th, 2002, 7:49 pm
-
- Posts: 282
- Joined: November 8th, 2002, 8:12 am
- Location: NJ
- Contact:
-
- Posts: 282
- Joined: November 8th, 2002, 8:12 am
- Location: NJ
- Contact: