[Bug 23946] Lift the ban on query parts in “blob:” URIs

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

--- Comment #15 from Manuel Strehl <org.w3@manuel-strehl.de> ---
> Like I said, I think that treating "?" special, by treating it as query
> delimiter, in data URLs will lead to more surprising behavior and subtle
> bugs than not doing so. But it's a judgement call I agree.
Well, the _hash_ not being parsed in data: URIs as fragment in Chrome certainly
puzzled some, at least there are already three duplicates to this bug:

http://code.google.com/p/chromium/issues/detail?id=123004

I'd like to think, that query parts will be no different once there's a use
case for reacting to them from within the data:-URI-referenced resource. (That
is, I think many developers simply haven't experienced yet, whether '?' is or
is not special in data: URIs.)

The remaining question is twofold, a fundamental and a pragmatic part:

1. How does a generic URL look like, scheme:any-stuff or
scheme:hier?query#fragment? It's my understanding so far, that the first is the
basic definition of an URI, which also allows, e.g., URNs like isbn:, while the
second is, what URLs look like. Hence, blob-_URLs_ should handle '?' and '#'
specially. Of course, if I'm misguided here, that point is invalid.

2. How do developers use the blob: URLs? E.g., will there be significant use
cases, what would be the more surprising behaviour, ... With my anecdotal
evidence drawn from the data: URL / fragment identifier analogy above, I'd
still argue for treating '?' specially, but I haven't got more profound data to
back this. Just my guts.

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

Received on Wednesday, 4 December 2013 21:58:06 UTC