As for Custom Elements, I think the following is one of the Action Items:
https://github.com/w3c/webcomponents/issues/287
Could someone add a missing action item to GitHub Issues if it exists?
As for the Shadow DOM spec, I'm updating the spec so that it adapts the
Slots and other changes which
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25097
Anne ann...@annevk.nl changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25097
Julian Reschke julian.resc...@gmx.de changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29049
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16137
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Resolution|LATER |MOVED
--- Comment #4
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22370
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25223
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22130
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Resolution|LATER |MOVED
--- Comment #4
https://www.w3.org/Bugs/Public/show_bug.cgi?id=11528
Joshua Bell jsb...@google.com changed:
What|Removed |Added
CC||jsb...@google.com
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21836
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Resolution|LATER |MOVED
--- Comment #6
https://www.w3.org/Bugs/Public/show_bug.cgi?id=1
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Resolution|LATER |MOVED
--- Comment #5
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28067
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28456
Joshua Bell jsb...@google.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Hey all,
Like Jungkee, I haven't been active editing the XHR spec. I too feel like
XHR L1 is very far from trivial. That is because the snapshot Domenic is
talking about is not what XHR L1 is supposed to be. XHR L1 is supposed to
be a state of what is actually implemented in released browsers at
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29049
Bug ID: 29049
Summary: Queue a microtask to unset active on transaction
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Hi All,
I was unable to attend the latest F2F so would like clarification on what
the takeaway action items were and who is responsible for pushing them
forward. I don't believe this information was included in the minutes.
I heard there was agreement around Shadow DOM. Who is tasked with
On Aug 6, 2015 11:05 PM, Glen Huang curvedm...@gmail.com wrote:
This assumes you'll match
That's a good point. I agree for most APIs it's probably better to simply
use polyfill code for all browsers. But some APIs have some extra benefits
that might not be polyfillable. For example, the
On Mon, Aug 10, 2015 at 2:07 PM, Arthur Barstow art.bars...@gmail.com wrote:
Given Takeshi's status it seems premature to speculate.
The current [TR] is now mostly void of content although it might be good to
gut it even more as well as to add a clear note that indicates that work has
stopped
On 8/7/15 8:32 AM, Anne van Kesteren wrote:
On Fri, Aug 7, 2015 at 1:56 PM, Arthur Barstow art.bars...@gmail.com wrote:
Given this status, and in the absence of other feedback, I think the Streams
API should remain in WebApps' charter (at least for now). Then later, the
work may proceed (if
19 matches
Mail list logo