Re: type parameter of Document.open() (detailed review of the DOM)

Ian Hickson wrote:
> The risk of implementing this as Firefox does, of course, is lack of 
> compatibility with pages that are expecting HTML handling. To gain some 
> level of compatibility we have to, at a minimum, strip leading and 
> trailing space characters, and ignore any content after the first 
> semicolon.

For what it's worth, Gecko just uses the same function for parsing this 
string as it uses for the Content-Type HTTP header.

-Boris