[Bug 13787] Define fragment identifier processing. RFC 3023 is useless for this purpose. from bugzilla@jessica.w3.org on 2013-03-23 (public-html-bugzilla@w3.org from March 2013)

From: <bugzilla@jessica.w3.org>
Date: Sat, 23 Mar 2013 13:36:40 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-13787-2486-cQlrLQe2kQ@http.www.w3.org/Bugs/Public/>

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

--- Comment #4 from Anne <annevk@annevk.nl> ---
Fetch ignores the fragment identifier (it's up to whatever invokes Fetch to do
something with it). URL does care about serializing and exposing it via API
(there are many interoperability issues there :-(). Processing however seems in
the realm of HTML. E.g. navigate, but also <img>/<video> for the media fragment
stuff.

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

Received on Saturday, 23 March 2013 13:36:41 UTC