[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 from bugzilla@jessica.w3.org on 2013-10-23 (public-html-bugzilla@w3.org from October 2013)

From: <bugzilla@jessica.w3.org>
Date: Wed, 23 Oct 2013 19:17:04 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13720-2486-SllKLQGtdL@http.www.w3.org/Bugs/Public/>

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

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
   Target Milestone|2016 Q1                     |Unsorted
           Severity|normal                      |minor

--- Comment #10 from Ian 'Hixie' Hickson <ian@hixie.ch> ---
Ok so the plan here is to remove all occurrences of "javascript:" in the spec,
and move all the normative content to the Navigate algorithm, to a branch in
the step that says "If the new resource is to be fetched using HTTP GET or
equivalent...".

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

Received on Wednesday, 23 October 2013 19:17:06 UTC