Open
Bug 237419
Opened 21 years ago
Updated 2 years ago
Doctype is always null for XUL documents.
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
NEW
People
(Reporter: m.d.nauta, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040313 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7b) Gecko/20040313 DOM property document.doctype is always null for a XUL document, even when there is an explicit <!DOCTYPE window etc. before the root element. Reproducible: Always Steps to Reproduce: 1. Open a XUL document in DOMinspector. 2. Check the JavaScript Object for the doctype property. 3. Actual Results: The doctype is null. Expected Results: If there is a <!DOCTYPE window> then the document.doctype should be an object with system id etc.
Updated•21 years ago
|
Comment 1•21 years ago
|
||
This happens because XULContentSinkImpl::HandleDoctypeDecl just returns without creating an actual doctype node. So not a DOM problem... there is in fact no doctype in the DOM. I don't know what the document in the URL field has to do with this bug, by the way....
Assignee: general → hyatt
Status: UNCONFIRMED → NEW
Component: DOM: Core → XP Toolkit/Widgets: XUL
Ever confirmed: true
OS: Windows 98 → All
QA Contact: ian → shrir
Hardware: PC → All
Comment 2•21 years ago
|
||
(In reply to comment #1) > I don't know what the document in the URL field has to do with this bug, by the > way.... It's some XUL-file, in case someone wants to test and can't find some XUL on the fast.
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets
Updated•15 years ago
|
Assignee: hyatt → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•