On Thu, 14 Oct 2010 15:46:30 +0200, Olli Pettay olli.pet...@helsinki.fi
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
On Thu, Oct 14, 2010 at 9:23 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Fri, Oct 15, 2010 at 12:53 PM, Tony Gentilcore to...@chromium.org
wrote:
The simplest way to address this is probably to advertise support via
an agreed upon meta tag. e.g.
meta name=NavigatorSearchBoxSupport
On Thu, Oct 14, 2010 at 2:59 PM, Peter Kasting pkast...@google.com 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
On Fri, Oct 15, 2010 at 9:08 AM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
On Thu, Oct 14, 2010 at 2:59 PM, Peter Kasting pkast...@google.com
wrote:
This proposal is not by any means the totality of everything involved
with
instant-style support. It is only a
On Fri, Oct 15, 2010 at 12:17 PM, Tony Gentilcore to...@chromium.org 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
On 10/15/2010 02:45 PM, Anne van Kesteren wrote:
On Thu, 14 Oct 2010 15:46:30 +0200, Olli Pettay
olli.pet...@helsinki.fi 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
On Fri, Oct 15, 2010 at 9:35 AM, Aryeh Gregor
simetrical+...@gmail.comsimetrical%2b...@gmail.com
wrote:
On Fri, Oct 15, 2010 at 12:17 PM, Tony Gentilcore to...@chromium.org
wrote:
The app has the heuristics. The UA fetches the page and discards it if
the
page doesn't indicate support. As
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 event
On Fri, 15 Oct 2010 20:34:14 +0200, Nicholas Zakas nza...@yahoo-inc.com
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
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
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 sam...@ytterbrink.nu wrote:
Hi I have found something really
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 er...@google.com wrote:
How about using a Blob URL? See the discussion here:
12 matches
Mail list logo
