[wp-trac] [WordPress Trac] #11939: Make Script Elements HTML4 and XHTML compilant

[WordPress Trac]

#11939: Make Script Elements HTML4 and XHTML compilant
--------------------------+-------------------------------------------------
 Reporter:  hakre         |       Owner:           
     Type:  defect (bug)  |      Status:  new      
 Priority:  normal        |   Milestone:  3.0      
Component:  Validation    |     Version:  3.0      
 Severity:  normal        |    Keywords:  has-patch
--------------------------+-------------------------------------------------
Changes (by hakre):

  * priority:  low => normal
  * type:  feature request => defect (bug)
  * milestone:  Future Release => 3.0


Comment:

 Replying to [comment:7 azaozz]:
 > This is mostly a theoretical situation. I don't see what is fixed here.

 Fixed is: Compability of the webapplications output with the client
 software (Compbaility of WordPress and the Webborwer).

 > [...] Don't think there are any browsers currently in use that don't
 understand this doctype and would parse it as HTML 4 for example

 Okay, I see you have not understood

 a) why this fix has been provided and[[BR]]
 b) what this fix is addressing.

 I'll revert your changes to this tickets properties right away so your
 misleading conclusions do not hurt it. I hope you can live with it.

 Not all Browsers in use with WordPress (as by the docs) do fully support
 displaying XHTML as XML but do display XHTML documents as HTML.

 The following Problem is addressed:
 {{{
  * <script> and <style> elements in XHTML sent as text/html have to be
    escaped using ridiculously complicated strings.
 }}}

 As you can see that is an issue for XHTML documents. And yes, todays
 browsers in use with WordPress might parse XHTML as HTML and some might
 parse it as XML - but only under certain conditions. I do not really know,
 if it's at all the issue that any browser in use with WordPress will
 display the backend as XML.

 This partially covers a more general problem that is related to the XHTML
 doctype as well. I add it here, so you can better understand which
 problems you have to deal with when sending out XHTML documents as
 text/html:

 {{{
  * Current browsers are, for text/html content, HTML4 user agents (at
    best) and certainly not XHTML user agents. Therefore if you send
    them XHTML you are sending them content in a language which is not
    native to them, and instead relying on their error handling. Since
    this is not defined in any specification, it may vary from one user
    agent to the other.
 }}}

 Reference: [http://hixie.ch/advocacy/xhtml Sending XHTML as text/html
 Considered Harmful] by Ian Hickson (Currently editor of HTML 5).

 Background information about Firefox Parsers Status:

 Firefox Nightly builds ship with the HTML5 parser since May 13th.

 Priorior to that, Firefox parsed XHTML documents serverd as text/html (as
 done by wordrpress if my memory serves me well) with the previous HTML
 parser. The actual HTML version is 4.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/11939#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software