Allowing both blob URLs and data URLs for workers sounds like a great idea.
/ Jonas
On Fri, Oct 15, 2010 at 3:49 PM, Eric Uhrhane wrote:
> How about using a Blob URL? See the discussion here:
> https://groups.google.com/a/chromium.org/group/chromium-html5/tree/browse_frm/thread/4288931009182422
How about using a Blob URL? See the discussion here:
https://groups.google.com/a/chromium.org/group/chromium-html5/tree/browse_frm/thread/4288931009182422/12703ab802469702.
On Fri, Oct 15, 2010 at 3:17 PM, Samuel Ytterbrink wrote:
>
> Hi I have found something really frustrating with the specs.
Hi I have found something really frustrating with the specs. to show that I
at least read the blog about proposing features here is the questions and
answers:
*What is the problem you are trying to solve?*
To create sophisticated single file webpages.
*What is the feature you are suggesting to hel
On Fri, 15 Oct 2010 20:34:14 +0200, Nicholas Zakas
wrote:
In reading through the spec, it looks like this is legal in the event
stream:
event: foo
data: bar
And then processed as:
If the event name buffer is not the empty string but is also not a
valid event type name, as defined by the
In reading through the spec, it looks like this is legal in the event stream:
event: foo
data: bar
And then processed as:
>> If the event name buffer is not the empty string but is also not a valid
>> event type name, as defined by the DOM Events specification, set the data
>> buffer and the
On Fri, Oct 15, 2010 at 9:35 AM, Aryeh Gregor
> wrote:
> On Fri, Oct 15, 2010 at 12:17 PM, Tony Gentilcore
> wrote:
> > The app has the heuristics. The UA fetches the page and discards it if
> the
> > page doesn't indicate support. As pointed out this is suboptimal. Perhaps
> we
> > need a two p
On 10/15/2010 02:45 PM, Anne van Kesteren wrote:
On Thu, 14 Oct 2010 15:46:30 +0200, Olli Pettay
wrote:
may I wonder why on earth any new API, like
link.sizes uses PutForwards?
IMHO, PutForwards should be limited to the
awkward DOM0 APIs like window.location.
What's wrong with PutForwards?
On Fri, Oct 15, 2010 at 12:17 PM, Tony Gentilcore wrote:
> The app has the heuristics. The UA fetches the page and discards it if the
> page doesn't indicate support. As pointed out this is suboptimal. Perhaps we
> need a two phase indication of support. First OpenSearch indicates that the
> page
On Fri, Oct 15, 2010 at 9:08 AM, Aryeh Gregor
> wrote:
> On Thu, Oct 14, 2010 at 2:59 PM, Peter Kasting
> wrote:
> > This proposal is not by any means the totality of everything involved
> with
> > "instant"-style support. It is only a piece.
>
> It's hard to evaluate a proposal that doesn't ac
On Thu, Oct 14, 2010 at 2:59 PM, Peter Kasting wrote:
> This proposal is not by any means the totality of everything involved with
> "instant"-style support. It is only a piece.
It's hard to evaluate a proposal that doesn't actually do anything by
itself. I don't see any problems in principle w
On Thu, Oct 14, 2010 at 9:23 PM, Robert O'Callahan wrote:
> On Fri, Oct 15, 2010 at 12:53 PM, Tony Gentilcore
> wrote:
>>
>> The simplest way to address this is probably to advertise support via
>> an agreed upon meta tag. e.g.
>>
>>
>> The UA populates the API only if the page advertises suppor
On Thu, 14 Oct 2010 15:46:30 +0200, Olli Pettay
wrote:
may I wonder why on earth any new API, like
link.sizes uses PutForwards?
IMHO, PutForwards should be limited to the
awkward DOM0 APIs like window.location.
What's wrong with PutForwards?
--
Anne van Kesteren
http://annevankesteren.nl/
12 matches
Mail list logo
