As discussed during last week's f2f meeting, WebApps will meet on
November 11-12 (Monday and Tuesday) at the annual TPAC meeting week,
which is in Shenzhen China this year:
http://www.w3.org/2013/11/TPAC/
WebApps meeting and agenda page is currently just a skeleton
Microsoft supports this.
-Original Message-
From: Arthur Barstow [mailto:art.bars...@nokia.com]
Sent: Saturday, April 27, 2013 7:31 AM
To: public-webapps
Subject: CfC: publish FPWD of UI Events; deadline May 4
As discussed during WebApps' April 25 meeting, this is a Call for Consensus
I’d like to propose we start a call to begin to work toward resolving the final
bugs in the spec and for other business related to getting DOM L3 Events to CR.
On the call we can workout what subsequent meetings we should also arrange.
Does next Tuesday (May 7th), at 11 am PST work your you?
Hi,
I noticed that there's not any clarification in the Decorations spec about
applying multiple decorators to a single element.
Example:
.headline[access-type=premium] {
decorator: url(#premium-decorator);
}
.headline[content-type=video] {
decorator: url(#video-decorator);
}
h3
On Mon, Apr 29, 2013 at 1:07 PM, Sam L'ecuyer s...@cateches.is wrote:
I noticed that there's not any clarification in the Decorations spec about
applying multiple decorators to a single element.
Example:
.headline[access-type=premium] {
decorator: url(#premium-decorator);
}
Per standard CSS rules, the latter declaration would win in the
cascade, and so only #video-decorator would be applied. If
'decorator' can apply multiple values, they have to be done in a
single line, not across declarations like this.
That's what I assumed. I was mostly trying to clarify
On Mon, Apr 29, 2013 at 12:59 PM, Travis Leithead
travis.leith...@microsoft.com wrote:
I’d like to propose we start a call to begin to work toward resolving
the final bugs in the spec and for other business related to getting DOM L3
Events to CR. On the call we can workout what subsequent
Google supports this.
On Mon, Apr 29, 2013 at 11:03 AM, Travis Leithead
travis.leith...@microsoft.com wrote:
Microsoft supports this.
-Original Message-
From: Arthur Barstow [mailto:art.bars...@nokia.com]
Sent: Saturday, April 27, 2013 7:31 AM
To: public-webapps
Subject: CfC:
Hi Ted!
Thanks for the kudos. We Shadow DOM elves are hard at work on making
the world a better place :)
I think you're raising good questions. I am sensitive of the fact that
you are just starting the journey into the shadows and volunteer to be
your Aragorn.
Yes, Shadow DOM is fairly complex,
On Mon, Apr 29, 2013 at 3:00 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
As far as implementation complexity, content select, distribution
APIs, and shadow are trivial, compared to the event handling and
representation of the composed tree. Hoping to alleviate this, I wrote
all
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21555
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
On Mon, Apr 29, 2013 at 3:14 PM, Blake Kaplan mrb...@gmail.com wrote:
On Mon, Apr 29, 2013 at 3:00 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
As far as implementation complexity, content select, distribution
APIs, and shadow are trivial, compared to the event handling and
On Mon, Apr 29, 2013 at 3:26 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
I wonder if it would be helpful for me to specify exactly where the
distribution/composition integrity must be ensured
(https://www.w3.org/Bugs/Public/show_bug.cgi?id=20141)? This should
help implementers to build a
In put and add method of object store and index, DataCloneError and
DataError are immediately throw before executing IDBRequest. It seems good
that exception are throw immediately, but in practical use case, these
exception are in async workflow (inside transaction callback). Exception
break the
14 matches
Mail list logo
