Closed Bug 42270 Opened 25 years ago Closed 25 years ago

page not rendering correctly; comment seen

Categories

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

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

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: Brade, Assigned: rickg)

References

(
URL
)

Details

(Whiteboard: [nsbeta2+][dogfood+]fix in hand)

go to bugzilla.mozilla.org notice that the "Mozilla bug" link near the top is very long and includes a comment containing JS as well as the edit field and Show button. This page renders "properly" in 4.x. Someone on irc suggested that recent parser changes may have broken this. This particular page is unusable for me.
this is causing layout problems on lots of pages. I noticed that if I download the html, then delete the first line (The DOCTYPE declaration) then the page lays out just fine!
Bug in strictDTD. Marking nsbeta2+ (fix in hand) due to severity.
Keywords: dogfood, nsbeta2
Whiteboard: fix in hand
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: fix in hand → [nsbeta2+][dogfood+]fix in hand
Fixed by allowing <script> into both block and inline. The bug was the at the <script> element erroneously acted like a <block>. Oops.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
*** Bug 42268 has been marked as a duplicate of this bug. ***
*** Bug 42291 has been marked as a duplicate of this bug. ***
is this bug causing Unordered list items to be displayed without newlines? <ul> <li>1 <li>2 </ul> this is showing up as "12" on pages that have a doctype declared. try http://warp/client/im/
The lack of newlines problem is covered in bug 42312.
I'm not sure I understand this bug. The decription talks about the "mozilla bug link near the top" but I don't know what that is. However the summary talks about "comment seen". That I can relate to. I see the entire npl comment appearing above the mozilla.org banner. So I'm presuming that that is what the bug is referring to. If my interpretation of the bug is correct, then I'm reopening this report. I'm still seeing the comment on a build from 6-13 at around 5PM whereas rickg's comment said that his fix went in on 6-12.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Steve--I too saw that comment at the top of the page (license). That is not the same comment as the one that was initially reported. However, after I reloaded the page, I was unable to reproduce the problem (I haven't seen the license comment since).
Target Milestone: --- → M17
This is exactly what I was reporting in bug 42268. I have included to that bug a second example which doesn't disappear after reloading.
The bugzilla problem was related to a bug in the StrictDTD. The other comment bug that has been running around lately (42268) had to do with a bug in the parser. The bugzilla issue was resolved (42268) is fixed in my tree awaiting a chance to checkin. Joseph Elwell: the issue mention is completely unrelated, but also fixed and ready to land.
Status: REOPENED → ASSIGNED
*** Bug 42268 has been marked as a duplicate of this bug. ***
*** Bug 42340 has been marked as a duplicate of this bug. ***
Landed fix. Please retest.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
*** Bug 42778 has been marked as a duplicate of this bug. ***
*** Bug 42787 has been marked as a duplicate of this bug. ***
fixed 2000-06-28-21-M17 : Win98 2000-06-29-14-M17 : Mac Linux build not working, will test later.
Also fixt on 2000-07-06-08-M17 - Linux marking verified.
Status: RESOLVED → VERIFIED
*** Bug 44586 has been marked as a duplicate of this bug. ***
Just a note to this, Meta tags rendered in the body of a document with this build: 2000-07-05-09-M17 on Win9x A week after this was marked fixed according to janc's comments on 06/29... However I haven't been able to reproduce it, it still happenned.
You need to log in before you can comment on or make changes to this bug.