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
Hi Mohamed,
On Jun 6, 2009, at 09:52 , mozer wrote:
Sorry for disturbing
Don't pretend you're sorry :)
there is a bunch of space problem in the spec
You expect space problems from a spec called WARP.
probably it is only depending on your build process
No, it's faulty cut and paste
Hi Thomas,
On Jun 9, 2009, at 09:59 , Thomas Roessler wrote:
1. The definitions section seems to introduce instantiated
components as a first class object that is granted access.
That is correct, I have changed it throughout the spec to talk only of
execution scopes.
2. It would be
On Mon, 15 Jun 2009 04:36:28 +0200, Mark Nottingham m...@mnot.net wrote:
Content providers wanted the flexbility of not having to list every
header in advance. Both so debugging headers and such would not have
to be exposed and to reduce the payload.
Which content providers? How much extra
I'm forwarding the following comments on behalf of Martin Nilsson, of
Opera Software, with his permission, to be addressed as part of the LC
review.
Kind regards,
Marcos
==
Section 5.3: Why not mandate all paths to be UTF-8? I really hate the
notion of If an author chooses to use
On Mon, 15 Jun 2009, Cameron McCormack wrote:
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
Hi all,
Within the Geolocation Working Group we've been discussing a few
different methods of securing the location API, one of which is
described below by Doug Turner [1]:
On May 21, 2009, at 6:02 PM, Doug Turner wrote:
got some feedback on this. this isn't how it works today, but I
I think this suggestion breaks with well established terms in
web application development. A short (and not very formal)
summary of these terms could be something like:
client-side web application:
- main part of presentation logic running as script in the
browser
- HTML user interface
On Mon, 15 Jun 2009 20:54:22 +0200, Mike Wilson mike...@hotmail.com wrote:
I think this suggestion breaks with well established terms in
web application development. A short (and not very formal)
summary of these terms could be something like: [...]
I note you did not define Web application.
Anne van Kesteren wrote:
On Mon, 15 Jun 2009 20:54:22 +0200, Mike Wilson
mike...@hotmail.com wrote:
Anne van Kesteren wrote:
You said Web application has been traditionally used to refer
to server-side applications. Is there any reference for this?
It seems more logical to call
On 16/06/2009, at 12:16 AM, Anne van Kesteren wrote:
On Mon, 15 Jun 2009 04:36:28 +0200, Mark Nottingham m...@mnot.net
wrote:
Content providers wanted the flexbility of not having to list
every
header in advance. Both so debugging headers and such would not
have
to be exposed and to
11 matches
Mail list logo
