Hi,
Apparently there has been discussions about hats and cats selector combinators
in www-style:
http://lists.w3.org/Archives/Public/www-style/2014Feb/0032.html
In that Tab (Atkins) from Google made a comment saying that Chrome will be
shipping Shadow DOM in the very near future:
http://lists.w
Good point.
My thinking is that I want somehow make HTML imports more like script than
HTML. What we need might be a separate content type than text/html for HTML
imports. It will prevent accidental inclusion of non-import HTML that is
more likely to have XSS hole.
We already has CORS to prevent
Dear WebApps Working Group Advisory Committee Representative,
Please ignore this call for exclusions for DOM4 (which is published exclusively
by the HTML Working Group).
We sent this due to a data error (to be fixed shortly).
Apologies for the noise,
Ian Jacobs
On Feb 4, 2014, at 11:06 AM, C
On Feb 4, 2014, at 3:40 PM, Philippe Le Hegaret wrote:
> Coralie,
>
> W3C DOM4 is only done in HTML, not WebApps. Is it possible to update the
> CfE?
Hi Philippe,
At first glance, a data bug is responsible. I'll alert the Webmaster and we'll
clean it up then cancel the CFE for Webapps.
Ian
Coralie,
W3C DOM4 is only done in HTML, not WebApps. Is it possible to update the
CfE?
Philippe
On Tue, 2014-02-04 at 18:06 +0100, Coralie Mercier wrote:
> Dear Advisory Committee representative,
>
> This is a W3C Patent Policy Call for Exclusions for the following
> Recommendation Track docume
On 2/4/14 11:48 AM, Arun Ranganathan wrote:
A web page using the FileSystem API in JavaScript and working in two separate
browser implementations seems like a good measure of interoperability
A good measure of interop is a test suite that actually tests edge cases
(something that a web page i
Dear Advisory Committee representative,
This is a W3C Patent Policy Call for Exclusions for the following
Recommendation Track document:
- W3C DOM4
(http://www.w3.org/TR/dom/),
exclusion opportunity ending on 5 April 2014 23:59 UTC
This specification was produced by the following groups:
On Feb 4, 2014, at 6:15 AM, Charles McCathie Nevile wrote:
> On Mon, 03 Feb 2014 19:09:53 +0400, Arthur Barstow
> wrote:
>
>> On 1/31/14 10:44 AM, ext Ian Clelland wrote:
>>> Hi Art,
>>>
>>> For what it's worth, theFile API: Directories and System is also
>>> implemented (and supported) by Ap
On Mon, 03 Feb 2014 19:09:53 +0400, Arthur Barstow
wrote:
On 1/31/14 10:44 AM, ext Ian Clelland wrote:
Hi Art,
For what it's worth, theFile API: Directories and System is also
implemented (and supported) by Apache Cordova[1]. The implementation is
essentially complete for mobile applica
On mar., 2014-02-04 at 17:16 +0900, Jungkee Song wrote:
> > The TR draft says that the URL of the editors draft is:
> > https://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html
> > I believe it is meant to be:
> > https://dvcs.w3.org/hg/xhr/raw-file/tip/xhr-1/Overview.html
> >
>
> That's right.
On 03.02.2014 21:58, Hajime Morrita wrote:
> Parser-made script means the tags and its contents that are
> written in HTML bytestream, not given by DOM mutation calls from
> scripts. As HTML Imports doesn't allow document.write(), it seems safe
> to assume that these scripts are statically given
On Feb 3, 2014 11:41 PM, "Dominique Hazael-Massieux" wrote:
>
> Hi,
>
> The TR draft says that the URL of the editors draft is:
> https://dvcs.w3.org/hg/xhr/xhr-1/raw-file/tip/Overview.html
> I believe it is meant to be:
> https://dvcs.w3.org/hg/xhr/raw-file/tip/xhr-1/Overview.html
>
That's right
12 matches
Mail list logo
