On 12/16/10 6:28 PM, Hajime Morita wrote:
Please let me clarify - which can be done without live-ness?
- 1. Changing the tree structure (adding/removing the child)
No.
- 2. Changing the attributes of the node (via setAttribute() or some
property access)
Yes.
- 3. Changing the style direc
Hi Tab,
On Fri, Dec 17, 2010 at 6:46 AM, Tab Atkins Jr. wrote:
>> Sure. I'm proposing that templates be completely dead. I'm also proposing
>> that, for a first cut, shadow trees be completely dead (in the "will throw
>> exception if you try to add or remove nodes" sense), unless we can figure
On Thu, Dec 16, 2010 at 10:09 PM, Pablo Castro
wrote:
>
> From: jor...@google.com [mailto:jor...@google.com] On Behalf Of Jeremy
> Orlow
> Sent: Thursday, December 16, 2010 2:35 AM
>
> >>In another thread (in the last couple days) we actually decided to remove
> timeouts from normal transactions s
On Thu, Dec 16, 2010 at 2:52 PM, Pablo Castro
wrote:
> I was going to file a bug on this but wanted to make sure I'm not missing
> something first.
>
> All the factory methods for ranges (e.g. bound, lowerBound, etc.) are in the
> IDBKeyRangeConstructors interface now, but I don't see the interf
BTW, I moved the use cases page to
http://wiki.whatwg.org/wiki/XBL2UseCases. I ran through the discussion
and attempted to update the wiki with interesting outcomes. Please
feel free to edit/comment.
:DG<
On Thu, Dec 16, 2010 at 1:46 PM, Tab Atkins Jr. wrote:
> On Thu, Dec 16, 2010 at 1:33 PM, B
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11564
Summary: Remove all references to manually populated indexes
Product: WebAppsWG
Version: unspecified
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Pri
I was going to file a bug on this but wanted to make sure I'm not missing
something first.
All the factory methods for ranges (e.g. bound, lowerBound, etc.) are in the
IDBKeyRangeConstructors interface now, but I don't see the interface referenced
anywhere. Who implements this interface, the Wi
From: jor...@google.com [mailto:jor...@google.com] On Behalf Of Jeremy Orlow
Sent: Thursday, December 16, 2010 2:35 AM
>>In another thread (in the last couple days) we actually decided to remove
>>timeouts from normal transactions since they can be implemented as a
>>setTimeout+abort.
>>
>>But
On Thu, Dec 16, 2010 at 1:33 PM, Boris Zbarsky wrote:
> On 12/16/10 1:00 PM, Dimitri Glazkov wrote:
>>
>> I agree that it's going to be difficult to get this right, but
>> semi-live templates (if you change it here, it will reflect on all
>> instances, but it you change it here, it won't) seem eve
On 12/16/10 1:00 PM, Dimitri Glazkov wrote:
I agree that it's going to be difficult to get this right, but
semi-live templates (if you change it here, it will reflect on all
instances, but it you change it here, it won't) seem even more
fragile.
Sure. I'm proposing that templates be completely
On Thu, Dec 16, 2010 at 12:23 PM, Olli Pettay wrote:
> On 12/16/2010 11:52 AM, Tab Atkins Jr. wrote:
>>
>> On Thu, Dec 16, 2010 at 10:40 AM, Boris Zbarsky wrote:
>>>
>>> On 12/15/10 11:29 AM, Dimitri Glazkov wrote:
That seems like an implementation detail. Metadata can be shared and
>>>
On Wed, Dec 15, 2010 at 10:53 PM, Maciej Stachowiak wrote:
>
> On Dec 15, 2010, at 11:14 AM, Boris Zbarsky wrote:
>
>>
>>
At least in Gecko's case, we still use XBL1 in this way, and those design
goals would apply to XBL2 from our point of view. It sounds like you have
entirely dif
On Thu, Dec 16, 2010 at 10:40 AM, Boris Zbarsky wrote:
> On 12/15/10 11:29 AM, Dimitri Glazkov wrote:
>>
>> That seems like an implementation detail. Metadata can be shared and
>> cloned as needed, just like styles in CSS.
>
> Sort of. It would need to be cloned as soon as the shadow tree is muta
On 12/16/2010 11:52 AM, Tab Atkins Jr. wrote:
On Thu, Dec 16, 2010 at 10:40 AM, Boris Zbarsky wrote:
On 12/15/10 11:29 AM, Dimitri Glazkov wrote:
That seems like an implementation detail. Metadata can be shared and
cloned as needed, just like styles in CSS.
Sort of. It would need to be clo
On Thu, Dec 16, 2010 at 10:40 AM, Boris Zbarsky wrote:
> On 12/15/10 11:29 AM, Dimitri Glazkov wrote:
>>
>> That seems like an implementation detail. Metadata can be shared and
>> cloned as needed, just like styles in CSS.
>
> Sort of. It would need to be cloned as soon as the shadow tree is muta
On 12/15/10 10:53 PM, Maciej Stachowiak wrote:
Are they really contradictory?
Good question. ;)
If they aren't, great.
Personally, I think it would be a huge win if XBL2-based components could be
more scalable than ones written in pure JavaScript using vanilla DOM calls.
That way, XBL2 co
On 12/15/10 11:29 AM, Dimitri Glazkov wrote:
That seems like an implementation detail. Metadata can be shared and
cloned as needed, just like styles in CSS.
Sort of. It would need to be cloned as soon as the shadow tree is
mutated, right? That seems like very fragile behavior from a web auth
Hi Doug and All，
I am Pan Songbai, from Chinaunicom which is one of the largest telecom
company in China， now I am studying key-Vale database and interested in
W3C spec， so I want to become an editor，Thanks.
Best regards,
Cooper
/* 潘松柏
* 中国联通集团研究院
* Tel: 010-6879-9587; 186-0110-300
On Thu, 16 Dec 2010 14:51:39 +0100, Robin Berjon wrote:
On Dec 14, 2010, at 22:24 , Dimitri Glazkov wrote:
Looking at the use cases and the problems the current XBL2 spec is
trying address, I think it might be a good idea to rename it into
something that is less legacy-bound?
I strongly objec
On Dec 14, 2010, at 22:24 , Dimitri Glazkov wrote:
> Looking at the use cases and the problems the current XBL2 spec is
> trying address, I think it might be a good idea to rename it into
> something that is less legacy-bound?
I strongly object. We have a long and proud tradition of perfectly horr
In another thread (in the last couple days) we actually decided to remove
timeouts from normal transactions since they can be implemented as a
setTimeout+abort.
But I agree that we need a way to abort setVersion transactions before
getting the callback (so that we implement timeouts for them as we
21 matches
Mail list logo
