For DOM Core Ms2ger and I (and some others on IRC) decided to introduce a
subtle distinction between fire and dispatch. Dispatching is actually
going through the list of event targets with an initialized event whereas
firing is initializing the event and then dispatching it.
E.g. a
On Tue, 22 Feb 2011 20:19:33 +0100, Richard L. Barnes rbar...@bbn.com
wrote:
Mark's XHR2-Secure proposal satisfies the requirement by explicitly
listing the headers that are secure (I'll assume the enumeration stays,
though it doesn't necessarily have to). Any header name that is
On Thu, 24 Feb 2011 14:43:47 +0100, Richard L. Barnes rbar...@bbn.com
wrote:
On Feb 24, 2011, at 6:53 AM, Anne van Kesteren wrote:
Would this not mean that for each new header introduced servers would
have to check an XHR2-secure header in addition to it to make sure it
is not being
The File API spec should say that FileError and FileException interface
objects must be available when the global object is a WorkerGlobalScope
object.
--
Simon Pieters
Opera Software
On 24.02.2011 15:00, Anne van Kesteren wrote:
On Thu, 24 Feb 2011 14:43:47 +0100, Richard L. Barnes rbar...@bbn.com
wrote:
On Feb 24, 2011, at 6:53 AM, Anne van Kesteren wrote:
Would this not mean that for each new header introduced servers would
have to check an XHR2-secure header in addition
(bcc to public-html and public-device-apis; please follow-up on
public-webapps)
Hi,
As part of a European research project I'm involved in [1], I've
compiled a report on the existing technologies in development (or in
discussion) at W3C for building Web applications and that are
particularly
On Feb 24, 2011, at 6:53 AM, Anne van Kesteren wrote:
On Tue, 22 Feb 2011 20:19:33 +0100, Richard L. Barnes rbar...@bbn.com wrote:
Mark's XHR2-Secure proposal satisfies the requirement by explicitly listing
the headers that are secure (I'll assume the enumeration stays, though it
doesn't
Hi Dom,
It looks quite nice as a way to organize a large lot of information. I'm sure I
will be making use of this often as I seem often to get confused by the number
of W3C projects on going and the proper jurisdiction as specific concerns may
arise. A couple of quick reactions:
I'm not sure
On Wednesday, February 23, 2011 8:21 AM, Arthur Barstow wrote:
Anne and Ms2ger (representing Mozilla Foundation) have continued to work
on the DOM Core spec and they propose publishing a new Working Draft of
the spec:
http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html
As such, this
Hi Dom,
This is really helpful - thanks for making this!
(I'm also working on some EU research projects, and I keep mentioning W3C specs
which no-one else has heard of, so this is a good resource to point researchers
and developers at.)
I think a 3-monthly update would also be worth doing
Hi Ian, All,
Given the information below, I think it would be useful to move this
spec to a test-ready state. That is, publish it as a Last Call Working
Draft now and if there are known issues, document them in the Status of
the Document Section. Then, after a fixed review period, if no
Hi Ian, All,
Given the information below, I think it would be useful to move this
spec to a test-ready state. That is, publish it as a Last Call Working
Draft now and if there are known issues, document them in the Status of
the Document Section. Then, after a fixed review period, if no
On Thu, 24 Feb 2011 19:26:19 +0100, Adrian Bateman
adria...@microsoft.com wrote:
I'm concerned about the working group endorsing a working draft with
phrasing like The timeStamp attribute must be useless. I understand
there are issues related to this (e.g. ISSUE-172) but this doesn't seem
On 2/24/11 9:19 AM, Simon Pieters wrote:
The File API spec should say that FileError and FileException
interface objects must be available when the global object is a
WorkerGlobalScope object.
Simon: duly noted.
-- A*
I support this publication.
- Maciej
On Feb 23, 2011, at 8:20 AM, Arthur Barstow wrote:
Anne and Ms2ger (representing Mozilla Foundation) have continued to work on
the DOM Core spec and they propose publishing a new Working Draft of the spec:
As we've been updating our WebSockets prototype [1] in line with the latest
protocol
changes we've been thinking about how the binary support that the protocol now
includes should be reflected in the API. I added the following comment to the
bug:
At Microsoft, we've been reviewing how the
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10381
Pablo Castro pablo.cas...@microsoft.com changed:
What|Removed |Added
Status|NEW |RESOLVED
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11552
Jeremy Orlow jor...@chromium.org changed:
What|Removed |Added
Status|NEW |RESOLVED
On Thursday, February 24, 2011 2:37 PM, Anne van Kesteren wrote:
On Thu, 24 Feb 2011 19:26:19 +0100, Adrian Bateman
adria...@microsoft.com wrote:
I'm concerned about the working group endorsing a working draft with
phrasing like The timeStamp attribute must be useless. I understand
there
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12179
Summary: We should spec the order in which version change
events fire
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Hi, Anne-
I object to publishing a Working Draft of the DOM Core spec that
includes DOM Events.
Introducing conflicting specifications that cover the same materials
dramatically harms interoperability, and the idea of competing
specifications is an anti-pattern when it comes to
On Thu, 24 Feb 2011, Arthur Barstow wrote:
Given the information below, I think it would be useful to move this
spec to a test-ready state. That is, publish it as a Last Call Working
Draft now and if there are known issues, document them in the Status of
the Document Section. Then, after
On Thu, Feb 24, 2011 at 5:46 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 24 Feb 2011, Arthur Barstow wrote:
Given the information below, I think it would be useful to move this
spec to a test-ready state. That is, publish it as a Last Call Working
Draft now and if there are known issues,
Hi Dom,
This looks like a very useful document.
On the voice/multimodal side, in addition to the HTML-Speech XG, you will
definitely want to add some of the Voice Browser Working Group and Multimodal
Interaction Working Group specs, specifically:
1. Multimodal Architecture and Interfaces, for
On 2/24/11, Anne van Kesteren ann...@opera.com wrote:
For DOM Core Ms2ger and I (and some others on IRC) decided to introduce a
subtle distinction between fire and dispatch. Dispatching is actually
going through the list of event targets with an initialized event whereas
firing is initializing
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12180
Summary: give the name of url to download the Jetty server
Product: WebAppsWG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#top
26 matches
Mail list logo
