Last Comment Bug 45832 - DOCTYPE is ignored if not at the very beginning of the document
: DOCTYPE is ignored if not at the very beginning of the document
Status: VERIFIED FIXED
nsbeta3+ fix waiting.
: regression
Product: Core
Classification: Components
Component: HTML: Parser (show other bugs)
: Trunk
: All All
: P3 normal (vote)
: M18
Assigned To: rickg
: Jan Carpenter
: Andrew Overholt [:overholt]
Mentors:
Depends on:
Blocks: 34662
  Show dependency tree / graph
 
Reported: 2000-07-18 23:06 PDT by Pierre Saslawsky
Modified: 2000-10-24 21:18 PDT (History)
3 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---

Attachments
testcase (494 bytes, text/html)
2000-07-18 23:06 PDT, Pierre Saslawsky 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Pierre Saslawsky 2000-07-18 23:06:24 PDT 
- Extracted from bug 45804.
- Tested on the Mac but it must be a cross-platform problem.

A regression was introduced between M17 06/28 and M17 06/30: if spaces are 
inserted before the DOCTYPE declaration, the declaration is ignored.

See the testcase that I'm going to attach.
Comment 1 Pierre Saslawsky 2000-07-18 23:06:45 PDT 
Created attachment 11556 [details]
testcase
Comment 2 David Baron :dbaron: ⌚️UTC-8 2000-07-19 07:48:08 PDT 
I suspect this would be fixed by the DOCTYPE parsing code I attached to bug
44340.
Comment 3 harishd 2000-08-08 12:20:11 PDT 
A common problem that should probably be fixed for beta3.
Comment 4 Nisheeth Ranjan 2000-08-16 11:16:10 PDT 
Marking nsbeta3-
Comment 5 rickg 2000-08-22 10:51:14 PDT 
Trivial fix waiting in my tree.
Comment 6 rickg 2000-08-24 10:25:29 PDT 
Moving back to nsbeta3+. Easy fix in my tree.
Comment 7 rickg 2000-08-30 16:52:57 PDT 
Setting correct milestone.
Comment 8 rickg 2000-09-11 10:36:41 PDT 
My error was that I didnt set the parse process up correctly to ignore ws.
Comment 9 please use i a n @ h i x i e . c h instead 2000-10-24 21:18:54 PDT 
Er, not vtrunk, just plain VERIFIED, since it was fixed before branching!
Note You need to log in before you can comment on or make changes to this bug.