Hello,
I am writing to seek interest of adding a set of window attributes in
the html5 specs
to let browser expose timing-related information of a page.
Many web pages/apps these days use javascript to measure component/page
latencies. Some
open source project has also been trying to make i
Thanks - a few replies below.
On 14/06/2009, at 10:24 PM, Anne van Kesteren wrote:
On Sun, 14 Jun 2009 03:58:31 +0200, Mark Nottingham
wrote:
As I said, I raised have raised substantive issues before:
http://lists.w3.org/Archives/Public/public-appformats/2008Jan/0226.html
and don't believe
Ian Hickson:
> Oh. Wouldn't it make more sense for JS compatiblility to have float be
> 64-bit? It seems bad to have a type that is 32-bit but then have its most
> common implementation not throw an exception or anything if setting a
> number that is 64-bit into it.
When converting Number value
On Mon, 15 Jun 2009, Cameron McCormack wrote:
> Ian Hickson:
> > How do I know when to use float or double, for types that are supposed to
> > represent infinite range? Should I just make everything double?
>
> If you want more range, sure, use double. Web IDL doesn’t have an
> arbitrary precis
Ian Hickson:
> How do I know when to use float or double, for types that are supposed to
> represent infinite range? Should I just make everything double?
If you want more range, sure, use double. Web IDL doesn’t have an
arbitrary precision numeric type. But double specifically means 64-bit
IEE
On Mon, 15 Jun 2009, Cameron McCormack wrote:
>
> I’ve added a distinct double type, as exists in OMG IDL:
>
> http://dev.w3.org/2006/webapi/WebIDL/#idl-double
> http://dev.w3.org/2006/webapi/WebIDL/#es-double
> http://dev.w3.org/2006/webapi/WebIDL/#java-double
How do I know when to use flo
Hi,
Oops, it looks like I have a few more points to make on path resolution.
These comments apply to the editor's draft 11 June 2009 version of the
Widgets 1.0: Packaging and Configuration specification.
Comments apply to the "Rule for finding a file within a widget package"
section in 9.1 P
Cameron McCormack:
> (Also I see that you’re using the “string” and “wstring”, and L"wide
> string" values. Are you of the opinion that Web IDL should introduce
> those instead of DOMString?)
Shiki Okasaka:
> In my opinion, it would be nice if we can use the keyword 'string' as
> the same meaning
Anne van Kesteren:
> For longitudes at least Geolocation needs high precision floating
> point values. We can either introduce the double type in Web IDL or
> just make float map always map to the 64 bit variant (as it already
> does for ECMAScript as I understand things). I don't feel strongly
> e
http://dev.w3.org/2006/webapi/FileUpload/publish/FileAPI.xhtml
Note, I expect all of my comments here to be of an editorial nature.
In the Abstract:
> use of appropriate [DOM]DOM methods should return a FileList object,
[DOM]DOM has no markup and seems very out of place.
> have the ability to m
On Sun, 14 Jun 2009 03:58:31 +0200, Mark Nottingham wrote:
> As I said, I raised have raised substantive issues before:
>http://lists.w3.org/Archives/Public/public-appformats/2008Jan/0226.html
> and don't believe they were formally addressed (note that I'm using
> Process terminology here).
ISSUE-89: Reduce the length of the header names? [CORS]
http://www.w3.org/2008/webapps/track/issues/89
Raised by: Anne van Kesteren
On product: CORS
In
http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0643.html
Mark Nottingham suggests that we rename the headers used in the pro
A few comments:
On Sat, Jun 13, 2009 at 5:39 AM, Tyler Close wrote:
> On Fri, Jun 12, 2009 at 10:36 PM, Adam Barth wrote:
>>> Isn't your answer above only about client (user agent) behavior? I'd still
>>> like understand what the recommended/expected difference in server behavior
>>> should/might
13 matches
Mail list logo
