From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7) Gecko/20011221 I can't exactly tell what's wrong with this page and if this bug is already opened - the page is too complicated for me. But please take a look. Reproducible: Always
The page has a DOCTYPE, which will trigger strict rendering, but is littered with non-standard comment terminators, e.g. <!---UPDATE HIGHLIGHTS SECTION---------> See http://bugzilla.mozilla.org/show_bug.cgi?id=102127#c16 and http://bugzilla.mozilla.org/show_bug.cgi?id=102127#c17 for details of why this will cause problems. confirming ->Tech evangelism Contact details from the page source : <meta name="author" content="Andrew Golden"> <meta name="email" content="firstname.lastname@example.org">
Assignee: asa → doronr
Status: UNCONFIRMED → NEW
Component: Browser-General → US General
Ever confirmed: true
Product: Browser → Tech Evangelism
QA Contact: doronr → zach
Version: other → unspecified
Summary: Page looks awfully → ibm.com - Bad comments in strict mode causing problems
taking, issues related to DOCTYPE and layout have been communicated to IBM.
Assignee: doronr → bclary
*** Bug 126996 has been marked as a duplicate of this bug. ***
bc: If your taking this bug, shouldn't you set Accept bug so it is no longer marked as New?
only when i contact them. they have been contacted about general issues including doctypes and comments but i haven't followed up recently.
<!--UPDATE HIGHLIGHTS SECTION--> now - others like every IBM page
Severity: normal → trivial
Summary: ibm.com - Bad comments in strict mode causing problems → ibm.com - WebSphere app server - Bad comments in strict mode causing problems
Is this fixed? Looks same to me in Gecko and IE.
It seems that IBM has fixed this. The source no longer contains comments containing "--".
Status: NEW → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → FIXED
yep. fixed. thx.
Status: RESOLVED → VERIFIED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.