Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.javascript > #25562

Re: Checking Loading Status of Cross-Domain Child Window

Show key headers only | View raw

Joao Rodrigues wrote:

> On 24/07/2014 12:42, Win User wrote:
>> I am being challenged to use only Javascript on a document prepared in
>> XHTML Transitional
> 
> Firstly, I'd suggest to not waste your time writing XHTML documents,
> because web browsers have historically rendered XHMTL documents with a
> MIME type of text/html, no matter the 'application/xhtml+xml' MIME type
> was supplied, or the document started with the XHTML doctype [1].

Utter nonsense.  In fact, documents that have been served with a “Content-
Type: text/html …” header field have been rendered as erroneous (and 
therefore error-corrected) HTML no matter the DOCTYPE declaration.

Documents that have been served with “Content-Type: application/xhtml+xml …” 
(and compatible MIME media types) have either not been rendered at all 
(e.g., by IE/MSHTML 6.0 which displayed a download dialog instead) or they 
have been rendered as XHTML. [1]

> Nowadays, it seems that the major browsers truly support XHTML, only if
> the 'application/xhtml+xml' MIME type is supplied by the web server [2]

Netscape NGLayout/Mozilla Gecko was able to render XHTML documents served 
with “Content-Type: application/xhtml+xml …” as XHTML since its first 
version, released in 2001 [2] (XHTML became a W3C Recommendation in 2000 
[3]).  That was because Mozilla, the Netscape Communicator rewrite, already 
included an XML parser, using XUL for its chrome; XUL is still used by 
Mozilla-based products today [4].

Other layout engines, like Opera’s Elektra and Presto [5a], followed.  
MSHTML was the exception until before Internet Explorer/MSHTML 9.0. [5b]

Rendering a document as XHTML meant and means that an XML parser is used, 
and syntax errors that violate XML well-formedness cause a document not to 
be displayed; the error message is displayed instead [6][7].

> Therefore, if you write XHTML documents, you still need to serve HTML to
> the old browsers that don't understand "application/xhtml+xml",

Nonsense.  They can serve “HTML-compatible” XHTML documents with “Content-
Type: text/html”, forfeiting the advantages that XHTML has to offer on the 
client side.

People, sometimes misguided, did and do it all the time, partially based on 
“HTML-compatible XHTML” explained in XHTML 1.0 Appendix C [8], which was 
superseded by a Working Group Note [9].  Apparently the authors of parsers 
and layout engines have learned to deal with that, and whose who did not are 
obsolete.

Finally, HTML5, “A vocabulary and associated APIs for HTML and XHTML”, 
specifies an “XHTML syntax” for “XML resources” not served with “Content-
Type: text/html …”. [10]

_________
[1] [de] <http://dciwam.de/faq/xhtml/wann-auf-xhtml-umsteigen>
[2] see e.g. <http://www.webreference.com/xml/column58/index.html>
[3] <http://www.w3.org/TR/2000/REC-xhtml1-20000126/>
[4] <https://developer.mozilla.org/en-US/docs/Mozilla/Tech/XUL>
[5a] <http://www.opera.com/docs/history/presto/#facts>
[5b] <http://blogs.msdn.com/b/ie/archive/2010/11/01/xhtml-in-ie9.aspx>
[6] <https://developer.mozilla.org/en-US/docs/Mozilla_Web_Developer_FAQ#How_is_the_treatment_of_application.2Fxhtml.2Bxml_documents_different_from_the_treatment_of_text.2Fhtml_documents.3F>
[7] <http://www.w3.org/TR/2008/REC-xml-20081126/#dt-error>
[8] <http://www.w3.org/TR/2000/REC-xhtml1-20000126/#guidelines>
[9] <http://www.w3.org/TR/2009/NOTE-xhtml-media-types-20090116/#text-html>
[10] <http://www.w3.org/TR/2014/WD-html5-20140617/the-xhtml-syntax.html#the-xhtml-syntax>
-- 
PointedEars
FAQ: <http://PointedEars.de/faq> | SVN: <http://PointedEars.de/wsvn/>
Twitter: @PointedEars2 | ES Matrix: <http://PointedEars.de/es-matrix>
Please do not Cc: me. / Bitte keine Kopien per E-Mail.

Back to comp.lang.javascript | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Checking Loading Status of Cross-Domain Child Window Win User <winuser@ms.invalid> - 2014-07-24 15:42 +0000
  Re: Checking Loading Status of Cross-Domain Child Window Joao Rodrigues <groups_jr-1@yahoo.com.br> - 2014-07-24 19:02 -0300
    Re: Checking Loading Status of Cross-Domain Child Window Win User <winuser@ms.invalid> - 2014-07-24 22:40 +0000
      Re: Checking Loading Status of Cross-Domain Child Window Andreas Bergmaier <andber93@web.de> - 2014-07-25 01:28 +0200
        Re: Checking Loading Status of Cross-Domain Child Window Win User <winuser@ms.invalid> - 2014-07-25 00:34 +0000
          Re: Checking Loading Status of Cross-Domain Child Window Andreas Bergmaier <andber93@web.de> - 2014-07-25 04:31 +0200
    Re: Checking Loading Status of Cross-Domain Child Window Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2014-07-25 11:59 +0200

csiph-web