Closed Bug 318365 Opened 20 years ago Closed 20 years ago

cannot see the content of page

Categories

(Core :: DOM: HTML Parser, defect, P2)

Product:
Core
Component:
DOM: HTML Parser
Type:
defect

Tracking

()

Status:
RESOLVED INVALID
Milestone:
mozilla1.9alpha1

People

(Reporter: beehuatling, Assigned: mrbkap)

References

(
URL
)

Details

(Keywords: regression, testcase)

Attachments

(1 file, 1 obsolete file)

Minimal testcase
90 bytes, text/html
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051129 Camino/1.0b1+ Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051129 Camino/1.0b1+ no content when accesswww.bclai.net no problem when using firefox Reproducible: Always Steps to Reproduce: 1.just go to www.bclai.net 2. 3. Actual Results: nothing displayed Expected Results: able to access the home page
Using FF 1.5 (Windows), I don't see anything either. What version of FF were you using?
That said, viewing the source shows that the body tag is inside a <noframes> tag, which is completely invalid HTML.
(In reply to comment #1) > Using FF 1.5 (Windows), I don't see anything either. What version of FF were > you using? Hi, I am using FF(MAC) not FF(windows). And it works. Rgds
(In reply to comment #3) > Hi, > > I am using FF(MAC) not FF(windows). And it works. > > Rgds > Yes, but what *version*. On Mac, select the Firefox application menu and "About Firefox" You should a string that looks similar to the following: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Paste it here.
(In reply to comment #4) > (In reply to comment #3) > > Hi, > > > > I am using FF(MAC) not FF(windows). And it works. > > > > Rgds > > > Yes, but what *version*. On Mac, select the Firefox application menu and "About > Firefox" You should a string that looks similar to the following: Mozilla/5.0 > (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 > Paste it here. Hi, Will do that when i get home(i live in asia). That will be around 10 hours later. Thanks
(In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Hi, > > > > > > I am using FF(MAC) not FF(windows). And it works. > > > > > > Rgds > > > > > Yes, but what *version*. On Mac, select the Firefox application menu and "About > > Firefox" You should a string that looks similar to the following: Mozilla/5.0 > > (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 > > Paste it here. > > Hi, > > Will do that when i get home(i live in asia). That will be around 10 hours > later. > > Thanks > Hi Sorry, I have not been using firefox for quite a while. So i forgot that i am not on the latest. The version of the firefox that works is Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7 I have upgraded the firefox to the latest version and the behaviour is the same as camino. Guess it is core problem again. :( The version that i am using is : Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 I also tried safari and it works for safari. The version is Version 2.0.2 (416.13) thanks for your attention.
Assignee: mikepinkerton → nobody
Component: General → Layout
Keywords: regression
Product: Camino → Core
QA Contact: layout
Version: unspecified → 1.8 Branch
OS: MacOS X → All
Hardware: Macintosh → All
Summary: cannot see the content. OK when using firefox → cannot see the content of page
This isn't displaying because of the Javascript on this page: http://www.uow.edu.au/~lai/news.html The JavaScript linked to is a stat counter: http://www.statcounter.com/counter/counter.js
I should clarify. The original URL has a frame which goes to the URL I'm now setting as the bug's URL. Inside that, there is another frame which shows in FF 1.0, but does not show in FF 1.5 or at all on the 1.8 branch. Removing the Javascript from the page shows the frame (_news.html) and thus... "works".
URL: http://www.bclai.net → http://www.uow.edu.au/~lai/news.html
Blocks: 289537
This is a regression from bug 289537 -- we're creating a <body> for the image this ad code writes out, and hence not creating a frameset.
Assignee: nobody → mrbkap
Status: UNCONFIRMED → NEW
Component: Layout → HTML: Parser
Ever confirmed: true
QA Contact: layout → parser
Version: 1.8 Branch → Trunk
Blake, this might be something we need to fix on branch. :(
I don't know what this bug should be blocking (1.8.1? 1.8.0.1?) but fortunately, the fix is trivial.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.9alpha
Keywords: testcase
Attached patch Don't open <body> for <img> (obsolete) — — Splinter Review
This will "break" anybody who wants <img><script> to behave like <img><body><script>, but it's the best we're going to do for now (without something resembling a major rewrite of the way that we handle this invalid content).
Attachment #204703 - Flags: superreview?(jst)
Attachment #204703 - Flags: review?(jst)
It's worth seeing what IE's behavior is for the other tags bug 289537 touched...
I believe the list used in that bug was created using IE. I wonder if IE does something "special" for the frameset case as opposed to the script case.
Well, IE6 also doesn't show anything for the url testcase: http://www.uow.edu.au/~lai/news.html <img> <frameset rows="*"> <frame src="http://google.com"> </frameset> Generated source of IE6 is (IE6 is only showing the image here, not the frame): <html> <HEAD></HEAD> <BODY><IMG> <FRAMESET rows="*"><FRAME src="http://google.com" marginheight="0" noresize="" name="main"></FRAMESET></BODY> </html> Dom source of current trunk Mozilla build is: <HTML> <HEAD/> <BODY> <IMG/> </BODY> </HTML> So the site doesn't support IE6.
What about http://www.bclai.net ? Does IE6 show anything there? If we have compat with IE6 then we should just leave it as it is, imo.
(In reply to comment #17) > What about http://www.bclai.net ? Does IE6 show anything there? No, IE 6 displays a blank page there as well
Then I think this should be wontfix.
This does, however, work in Safari, which is I think why it was reported. It was reported on a Mac and that seems to be the only browser that will show it.
That sounds like a bug in Safari to me -- the HTML spec is very clear that an <img> tag implies a <body>.
(In reply to comment #21) > That sounds like a bug in Safari to me -- the HTML spec is very clear that an > <img> tag implies a <body>. > Filed. http://bugzilla.opendarwin.org/show_bug.cgi?id=5908
Comment on attachment 204703 [details] [diff] [review] Don't open <body> for <img> I should test compatibility before I patch, apparently.
Attachment #204703 - Attachment is obsolete: true
Attachment #204703 - Flags: superreview?(jst)
Attachment #204703 - Flags: review?(jst)
Marking this as INVALID. We're already compatible with IE, and this is a weird edge case where I think following IE's behavior makes more sense.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: