[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 #18 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
> 1)  Does javascript: evaluation still affect session history after this
>     change if it creates a new document?

Yeah. All that's really replaced is that instead of calling "fetch" we evaluate
a script and use its result as the resource's data, and there's a hack to fix
the URL to the previous URL.


> 2)  Does javascript: still run async after this change in all cases?

It runs in a separate task, if that's what you mean. (The previous state of the
spec with respect to this question was nonsensical. It ran the script literally
asynchronously, potentially in parallel with scripts running as part of tasks
run in the event loop!)


Please reopen the bug if there's anything else I should look at; I likely won't
see changes to this bug for months if it's closed (I only look at bugmail every
few weeks).

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

Received on Friday, 15 November 2013 20:27:58 UTC