https://www.w3.org/Bugs/Public/show_bug.cgi?id=27829
Hayato Ito changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28493
Bug ID: 28493
Summary: [Shadow]: Have a common interface between Document and
ShadowRoot
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21066
Hayato Ito changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27637
Hayato Ito changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27359
Hayato Ito changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
Cross-posting as is usual ...
What: IndieUI Task Force Teleconference
When: Wednesday 15 April
2:00 PMSan Francisco -- U.S. Pacific Time (PDT: UTC -7)
4:00 PMAustin -- U.S. Central Time(CDT: UTC -5)
5:00 PMBoston -- U.S. Eas
We found some timing issues with polyfill HTML Imports and native Custom
Elements in Chrome that made us force the Custom Elements polyfill when
HTML Imports is polyfilled. I don't remember the specifics, but I filed the
github issue to either track down and resolve the issues, or provide a flag
Just to close the loop, filed
https://github.com/webcomponents/webcomponentsjs/issues/289 to track the
specific Polymer web component polyfill blocker.
On Tue, Apr 14, 2015 at 5:38 AM, Anne van Kesteren wrote:
> On Wed, Apr 8, 2015 at 6:11 PM, Dimitri Glazkov
> wrote:
> > Thanks for the feedbac
On Tue, Apr 14, 2015 at 5:38 AM, Anne van Kesteren wrote:
> On Wed, Apr 8, 2015 at 6:11 PM, Dimitri Glazkov
> wrote:
> > Thanks for the feedback! While the iron is hot I went ahead and
> > created/updated bugs in the tracker.
>
> A problem I have with this approach is that with Shadow DOM (and m
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28491
Bug ID: 28491
Summary: [Shadow]: [Meta] Unblock Mozilla's shipping of Shadow
DOM
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
On 4/14/15 8:22 AM, Yves Lafon wrote:
I remember ArrayClass removed from NodeList for the reason of lack of
implementations, and even plans for implementation
It was removed because as things stand it's not web-compatible. Once
@@isConcatSpreadable exists in implementations, we could and sho
On 14 April 2015 at 14:29, Arthur Barstow wrote:
> [Bcc public-openw3c ]
>
> Hi All,
>
> In case you missed it, last February, Robin, Philippe and others (see [1]
> for a list of contributors) started a project to "capture the state of the
> discussion about modernising the tooling that supports
On Wed, Apr 8, 2015 at 6:11 PM, Dimitri Glazkov wrote:
> Thanks for the feedback! While the iron is hot I went ahead and
> created/updated bugs in the tracker.
A problem I have with this approach is that with Shadow DOM (and maybe
Web Components in general) there's a lot of open bugs. Of those bu
[Bcc public-openw3c ]
Hi All,
In case you missed it, last February, Robin, Philippe and others (see
[1] for a list of contributors) started a project to "capture the state
of the discussion about modernising the tooling that supports the making
of W3C standards".
The working document is
> On 10 Apr 2015, at 18:49, Boris Zbarsky wrote:
>
> On 4/10/15 8:53 AM, Yves Lafon wrote:
>> * Everything from old v1 expect ArrayClass which is not used, nor
>> implemented anywhere.
>
> It's implemented in Gecko and used for both DOMRectList and MediaList in
> Gecko, fwiw.
>
> I'm not s
The SysApps WG charter expired Oct 1 2014 and no re-chartering process is in
progress. Similar to Wayne Carr's CfC on Intel's SysApps specification,
https://lists.w3.org/Archives/Public/public-sysapps/2015Mar/0001.html, I am
issuing an informal CfC on moving the SysApps TCP and UDP Socket API to
16 matches
Mail list logo