[Bug 13720] Define javascript: processing entirely inline, and make it only happen in the navigation algorithm; then, remove special-casing elsewhere, and make it non-conforming in those places

https://www.w3.org/Bugs/Public/show_bug.cgi?id=13720

--- Comment #11 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Said branch should avoid "fetch" entirely, and run JS directly. This fixes one
bug which is that right now we try to execute javascript: async without a task,
oops.

We'll also have to change "Wait for one or more bytes to be available or for
the user agent to establish that the resource in question is empty" in
navigate.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 25 October 2013 18:05:13 UTC