- From: Daniel Bates <notifications@github.com>
- Date: Sat, 26 Jan 2019 14:12:47 -0800
- To: w3c/DOM-Parsing <DOM-Parsing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Saturday, 26 January 2019 22:13:08 UTC
The DOM Parsing spec does not specify whether the type argument passed to parseFromString() is case-sensitively or case-insensitively matched against MIME types. In absence of such a mention the spec. text falls back to a general statement that a reader should assume case-sensitive matching. It does not make sense (to me) that we should be performing case-sensitive matching for MIME types. MIME types are defined to be case-insensitive by <https://tools.ietf.org/html/rfc2045>. I suggest we change the spec. text: > The DOMParser constructor must return a new DOMParser object. > The parseFromString(str, type) method must run these steps, depending on type: > > "text/html" > ... To something like: > The DOMParser constructor must return a new DOMParser object. > The parseFromString(str, type) method must run these steps, depending on type case-insensitively matching one of the following MIME types: > > "text/html" > ... -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/DOM-Parsing/issues/40
Received on Saturday, 26 January 2019 22:13:08 UTC