Hi Maciej, Thanks for your attention!
> For reference: will the feature flag be comprehensive, or will parts of
the implementation/scaffolding be outside the ifdef?
It should be comprehensive. So it will.
Although some trivial inline stubs, like just returning null or false, or
even doing nothin
On Jan 29, 2013, at 6:22 PM, Hajime Morrita wrote:
> Hi folks,
>
> I'm going to implement "Custom Elements" standard behind
> ENABLE(CUSTOM_ELEMENTS) flag.
> https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html
For reference: will the feature flag be comprehensive, or will
On Tue, Jan 29, 2013 at 7:21 PM, Benjamin Poulain wrote:
> On Tue, Jan 29, 2013 at 6:22 PM, Hajime Morrita wrote:
>
>> I'm going to implement "Custom Elements" standard behind
>> ENABLE(CUSTOM_ELEMENTS) flag.
>> https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html
>>
>> Here is
On Tue, Jan 29, 2013 at 6:22 PM, Hajime Morrita wrote:
> I'm going to implement "Custom Elements" standard behind
> ENABLE(CUSTOM_ELEMENTS) flag.
> https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html
>
> Here is the tracking bug for the feature:
> https://bugs.webkit.org/show_
Hi folks,
I'm going to implement "Custom Elements" standard behind
ENABLE(CUSTOM_ELEMENTS) flag.
https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html
Here is the tracking bug for the feature:
https://bugs.webkit.org/show_bug.cgi?id=99688
Note that Mozilla is also working on i
5 matches
Mail list logo