On Tue, Oct 1, 2013 at 9:33 PM, Kyle Huey wrote:
> The File API specifies how to deal with fragment identifiers. It should
> also specify what to do with the query string. Presumably it should be
> ignored when looking up blob URIs.
This is also what http://fetch.spec.whatwg.org/#basic-fetch su
Ok, I was asking for a use case like the use you show, I didn't think about
iframes :-) It's good to me then.
El 02/10/2013 07:37, "Kyle Huey" escribió:
> Oh, sure. I'm not saying we should drop the query string entirely, I'm
> saying that blob:foo and blob:foo?bar should both load the same thin
Oh, sure. I'm not saying we should drop the query string entirely, I'm
saying that blob:foo and blob:foo?bar should both load the same thing. If
someone does and the script inside that blob
looks at bar and does processing on it that's fine.
- Kyle
On Wed, Oct 2, 2013 at 1:31 PM, pira...@gmai
Query can also be procesed by client-side javascript...
El 02/10/2013 07:25, "Kyle Huey" escribió:
> Well the query string is meant for the server, so what would you do with
> it?
>
> - Kyle
>
>
> On Wed, Oct 2, 2013 at 1:10 PM, pira...@gmail.com wrote:
>
>> Could it be procesed someway instead?
Well the query string is meant for the server, so what would you do with it?
- Kyle
On Wed, Oct 2, 2013 at 1:10 PM, pira...@gmail.com wrote:
> Could it be procesed someway instead?
> El 02/10/2013 03:34, "Kyle Huey" escribió:
>
> The File API specifies how to deal with fragment identifiers.
Could it be procesed someway instead?
El 02/10/2013 03:34, "Kyle Huey" escribió:
> The File API specifies how to deal with fragment identifiers. It should
> also specify what to do with the query string. Presumably it should be
> ignored when looking up blob URIs.
>
> - Kyle
>
The File API specifies how to deal with fragment identifiers. It should
also specify what to do with the query string. Presumably it should be
ignored when looking up blob URIs.
- Kyle
