- From: Philip Taylor <pjt47@cam.ac.uk>
- Date: Fri, 19 Feb 2010 10:44:44 +0000
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- CC: Boris Zbarsky <bzbarsky@MIT.EDU>, "public-html@w3.org" <public-html@w3.org>
Leif Halvard Silli wrote: > Philip Taylor, Thu, 18 Feb 2010 16:47:13 +0000: >> It's handled in HTML5 >> > (http://whatwg.org/html#between-doctype-public-and-system-identifiers-state) >> exactly like any other bogus character (i.e. forcing quirks mode), >> but Firefox appears to have a special case for "[" in this location >> (preventing quirks). > > When you say "Firefox appears to have", then you mean Firefox' HTML5 > implementation, I suppose? I meant the legacy / current default Firefox behaviour, i.e. not HTML5. >> http://www.freemanforman.co.uk/ >> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" >> [url=http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> >> >> http://symptomresearch.nih.gov/ >> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" []> > > Mister Taylor: That is a transitional doctype. The reason it triggers > quirks has to do with that, and is _not_ related to the "[]". Oops, hadn't noticed that - but in HTML5 the "[]" triggers the force-quirks flag so it is related to that string, regardless of the public identifier. In Firefox it seems to trigger some kind of force-*non*-quirks flag, to override the quirkiness of the public identifier. >> Filed as http://www.w3.org/Bugs/Public/show_bug.cgi?id=9071 > > Wonder why we needed two bug reports for this ... The other bug was about supporting an obscure SGMLism, or about an undefined set of "All DOCTYPE variants that trigger standards mode pre-HTML5". This one is just about a specific potential legacy compatibility issue with broken content that happens to have a "[" after the public identifier. -- Philip Taylor pjt47@cam.ac.uk
Received on Friday, 19 February 2010 10:45:14 UTC