The home page of the parody religion, Church of the Flying Spaghetti Monster, has serious issues with Webkit: almost all content below the main navigation refuses to display. Page displays with no problems in Safari. Not being that well-versed in coding and all that, I'm not exactly sure what's wrong, but if I had to venture a guess, I'd say it probably had something to do with handling of imported CSS or Javascript. Again, just a guess: I'll leave it up to the people who know this stuff to actually figure it out.
(In reply to comment #0) > The home page of the parody religion, Church of the Flying Spaghetti Monster, > has serious issues with Webkit: almost all content below the main navigation > refuses to display. Page displays with no problems in Safari. That last bit, of course, should be "Page displays with no problems in Firefox."
WebKit r18481 shows the pages on that site fine for me, with the exception of the home page, where something is broke.
I looked at this the other night and I'm wondering if this is really a bug in WebKit or not. There is less content when viewed in Safari/WebKit than Firefox because of an inline script that doesn't close the comment it opens with. Firefox/IE7 seem to ignore this and assume the comment ends at the end of the script and continues on and continues to render the page. Shipping Safari, ToT and Opera ignore the rest of the page. Remove the poorly coded script and everybody renders fine. #primary contains all of the posts and is floated left. Since we think that everything after that is commented out, we never render the div to clear it so .content collapses up like it should and results in the rendering we see.
(In reply to comment #3) > There is less content when viewed in Safari/WebKit than Firefox because of an > inline script that doesn't close the comment it opens with. Firefox/IE7 seem > to ignore this and assume the comment ends at the end of the script and > continues on and continues to render the page. Shipping Safari, ToT and Opera > ignore the rest of the page. Remove the poorly coded script and everybody > renders fine. Lets make a test case for this, then. I'd think we should match the browsers that have more market share than us on this if possible -- should help compatibility.
(In reply to comment #4) > > Lets make a test case for this, then. I'd think we should match the browsers > that have more market share than us on this if possible -- should help > compatibility. > Unfortunately, they seem to have corrected the bug on their end and I no longer have the copy I saved locally to figure this out and I can't seem to find a cached copy anywhere.
(In reply to comment #5) > Unfortunately, they seem to have corrected the bug on their end and I no longer > have the copy I saved locally to figure this out and I can't seem to find a > cached copy anywhere. Can you grab a copy of their home page (use Firefox to save as "Web Page, Complete") and then start removing "// -->" lines in the code until the issue is duplicated?
(In reply to comment #6) > Can you grab a copy of their home page (use Firefox to save as "Web Page, > Complete") and then start removing "// -->" lines in the code until the issue > is duplicated? I'm gonna try that tonight.
Created attachment 12713 [details] Testcase I managed to find a local copy of this after all (hooray being unorganized?). Here's a reduction. There should be two divs visible - a green one and a red one. WebKit only displays the green one up to where the script starts.
*** Bug 17412 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 16722 ***