Hi Arthur and WebAppsWG,
Status of Shadow DOM:
Update since the last TPAC:
- The new WD [1] was published.
I plan to address the followings in the next six months:
- Update the event path calculation algorithm [2]
- Resolve 'In Document' issues [3]
- Bring back 'shadow as function' to the spec
On 22 October 2014 20:55, Jonas Sicking jo...@sicking.cc wrote:
However I don't think that it makes sense for apps to commit to
displaying UI when there's an incoming push. I'm not sure what problem
that would solve?
It means the user is aware of incoming pushes, which alleviates two
On 10/22/14 6:27 PM, Paul Cotton wrote:
given the magnitude of the changes in [changeset], a new WD should be
published.
Can we please wait until after the TPAC week to publish the proposed
Streams heartbeat? Given the substantive changes being made here I
think it would be best to have a
- annevk@, feras.moussa@, domenic@, acolwell@, art.barstow@
23.10.2014, 15:06, Arthur Barstow art.bars...@gmail.com:
On 10/22/14 6:27 PM, Paul Cotton wrote:
given the magnitude of the changes in [changeset], a new WD should be
published.
Can we please wait until after the TPAC week to
On Oct 23, 2014, at 15:10 , cha...@yandex-team.ru wrote:
- annevk@, feras.moussa@, domenic@, acolwell@, art.barstow@
23.10.2014, 15:06, Arthur Barstow art.bars...@gmail.com:
On 10/22/14 6:27 PM, Paul Cotton wrote:
given the magnitude of the changes in [changeset], a new WD should be
On Thursday, October 23, 2014 9:16 AM, Costin Manolache wrote:
On Wed, Oct 22, 2014 at 10:19 PM, Shijun Sun shij...@microsoft.com wrote:
It'd be very helpful if PushRegistration can have a read-only attribute for
ExpirationTime or something like that. Webapps can be more proactive if the
From: Arthur Barstow [mailto:art.bars...@gmail.com]
I think recent threads about Streams provided some useful information about
the status and plans for Streams. I also think it could be useful if some set
of you were available to answer questions raised at the meeting. Can any of
you
Separate from heartbeat publication, we don't believe it is appropriate to
directly reference this spec in MSE until some questions are answered about how
streams will be represented.
Jerry
-Original Message-
From: David Singer [mailto:sin...@apple.com]
Sent: Thursday, October 23,
On Tue, Oct 21, 2014 at 7:25 AM, Erik Corry erikco...@google.com wrote:
* Push doesn't actually need SW's ability to intercept network
communications on behalf of a web page.
* You can imagine a push-handling SW that does all sorts of
complicated processing of notifications, downloading things
On Thu, Oct 23, 2014 at 2:27 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Tue, Oct 21, 2014 at 7:25 AM, Erik Corry erikco...@google.com wrote:
* Push doesn't actually need SW's ability to intercept network
communications on behalf of a web page.
* You can imagine a push-handling SW that
On 23 October 2014 04:10, John Mellor joh...@google.com wrote:
Can you elaborate? This would attach no penalty to developers who don't opt
in (at the one time cost of an additional permission prompt); and as I
explained above, developers who do opt in would indeed be incentivized to
always
On 22 October 2014 22:19, Shijun Sun shij...@microsoft.com wrote:
Thanks Martin. It'd be very helpful if PushRegistration can have a read-only
attribute for ExpirationTime or something like that. Webapps can be more
proactive if the ExpirationTime is set.
I was thinking that this was a
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27151
Bug ID: 27151
Summary: [imports]: Poor grammar in the 3.1 Import Dependent
section
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
13 matches
Mail list logo
