In 4.10.19.4 URL-encoded form data, The
application/x-www-form-urlencoded encoding algorithm,
it says:
> For each character in the entry's name and value, apply the following
> subsubsteps:
>
> If the character isn't in the range U+0020, U+002A, U+002D, U+002E,
> U+0030 to U+0039, U+0041 to U+005
On Mon, 18 Jan 2010 13:58:16 +0100, Ian Hickson wrote:
I'd like at some point to introduce some sort of "semantic" textContent
that handles , , , dir="", , , space-
collapsing, and newline elimination, but there hasn't been much
enthusiasm
around the idea, and it's not clear what else it wou
On Mon, 18 Jan 2010 16:24:46 +0100, Jeremy Keith
wrote:
Hixie wrote:
Finally on vCard, the final part of the extraction algorithm goes to
great trouble to guess what is the family name and what is the given
name. This guess will be broken for transliterated east Asian names
(CJKV that I know
I'm trying to understand the async and defer attributes of the script
tag. Unfortunately, since script execution is so intimately tied up
with HTML parsing, section 4.3.1 is particularly hard to make sense of.
I've got 3 questions, and 3 suggested clarifications to the spec.
Thanks to anyone wh
On Jan 15, 2010, at 12:05, Henri Sivonen wrote:
> I've located a Mozilla test case that seems to depend on the event loop task
> mapping of data: URL loads
> (http://mxr.mozilla.org/mozilla-central/source/layout/base/tests/chrome/test_bug533845.xul).
This was most likely a misdiagnosis.
--
He
