Closed Bug 79139 Opened 23 years ago Closed 22 years ago

Danawa Korea Strict mode page has extraneous -- in the comments

Categories

(Tech Evangelism Graveyard :: Other, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: marzio, Assigned: momoi)

References

()

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.19-2samix i686; en-US; rv:0.9+)
Gecko/20010507
BuildID:    20010507

HTML comment TAG parsing error.
example
<!------ comments ---->
... HTML contents ...


Reproducible: Always
Steps to Reproduce:
1.open above URL
2.save page
3.edit page
4. delete "--", then it is visiable, but delete again "--", then
  unvisiable


Actual Results:  some site is not visiable


good case :
<!-- comment -->
<!---- comment ---->

bad case :
<!---- comment -->
<!-- com -- ment -->
<!-- comment ---->
Changing summary from "Un visiable page" to "wrong number of "-"s in comments
makes part of page fail to render".

Over to parser for a try, but this probably a dupe.
Assignee: asa → harishd
Component: Browser-General → Parser
QA Contact: doronr → bsharma
Summary: Un visiable page → wrong number of "-"s in comments makes part of page fail to render
Whiteboard: DUPEME
possibly related to bug 52931

but have searched, and I dont see any obvious dups.
This is an error in the page, not the parser.  SGML comments start with -- and
end with --.  So:

<!-- this is commented -- this is not commented -- this is commented > this is
still commented because we never ended the last comment and furthermore the SGML
processing instruction is _not_ finished yet, since the ">" was commented --
this is not commented but still inside the SGML processing instruction > this is
after the end of the SGML processing instruction and not commented.

In quirks backwards-compatible mode we emulate the buggy behavior of NS 4.x and
various other browsers with regard to comments.  The page in question uses:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">

So we show it in strict mode, including strict comment parsing (bug 2749 was
finally fixed, implementing strict comment parsing in strict mode).

Over to evangelism -- that page is not HTML 4.0 compliant, though it claims to be...
Assignee: harishd → bclary
Status: UNCONFIRMED → NEW
Component: Parser → Evangelism
Ever confirmed: true
QA Contact: bsharma → zach
Summary: wrong number of "-"s in comments makes part of page fail to render → Strict mode page has extraneous -- in the comments
Whiteboard: DUPEME
Please correct me if I am wrong, but isn't a DOCTYPE without the URI supposed to
invoke Quirks mode?  Or is that only with the transitional DOCTYPEs?  Is there
anywhere where the DOCTYPE sniffing (as implemented) is documented?
I think it's documented on the bugzilla helper page and in the various bugs that
implemented it.  The current implementation is:

1)  No doctype, HTML version < 4.0 doctype ==> quirks
2)  HTML 4.0 Transitional doctype ==> quirks (no matter whether there is a URI)
3)  HTML 4.01 Transitional doctype _without_ uri ==> quirks
4)  HTML 4.01 Transitional doctype _with_ correct uri ==> strict
4)  anything else ==> strict
Priority: -- → P4
Assignee: bclary → momoi
Summary: Strict mode page has extraneous -- in the comments → Danawa Korea Strict mode page has extraneous -- in the comments
Assigning to Asia Evangelist
Component: Evangelism → Asian
Product: Browser → Tech Evangelism
Version: other → unspecified
works now.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Korean bugs. Moving to Other.
Component: Asian → Other
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.