On Sat, Sep 3, 2011 at 4:31 AM, Anne van Kesteren wrote:
>
> On Fri, 02 Sep 2011 20:47:27 +0200, Dimitri Glazkov
> wrote:
>> BTW, I really ought to put this "fears" list on the Wiki.
>
> Yeah that would probably be a good idea.
Done: http://wiki.whatwg.org/wiki/Custom_Tags_Analysis it still nee
On 3/09/11 4:47 AM, Dimitri Glazkov wrote:
On Fri, Sep 2, 2011 at 2:30 AM, Anne van Kesteren wrote:
Examples of elements that should not be replaced but could be changed by a
binding: Having a sortable binding for; Exposing cite="" on
; Turning a listing countries into a map.
Great! Let's go
On Sun, Sep 4, 2011 at 5:03 PM, Robert O'Callahan wrote:
> On Sun, Sep 4, 2011 at 1:56 PM, Dimitri Glazkov
> wrote:
>>
>> The offsetWidth query could've triggered an event
>> handler execution
>
> I don't think "offsetWidth" should be able to trigger synchronous execution
> of an event listener i
On Sun, Sep 4, 2011 at 1:56 PM, Dimitri Glazkov wrote:
> The offsetWidth query could've triggered an event
> handler execution
>
I don't think "offsetWidth" should be able to trigger synchronous execution
of an event listener in the content. How would that happen?
Rob
--
"If we claim to be with
On Sat, Sep 3, 2011 at 12:08 PM, Ian Hickson wrote:
> On Fri, 2 Sep 2011, Anne van Kesteren wrote:
>>
>> What we need is not a becomes="" attribute (that renames an element and
>> therefore forgoes its semantics) but rather a way to get complete
>> control over a semantic element and tweak aspects
On Sep 3, 2011, at 12:08 PM, Ian Hickson wrote:
> On Fri, 2 Sep 2011, Anne van Kesteren wrote:
>>
>> What we need is not a becomes="" attribute (that renames an element and
>> therefore forgoes its semantics) but rather a way to get complete
>> control over a semantic element and tweak asp
On Fri, 2 Sep 2011, Anne van Kesteren wrote:
>
> What we need is not a becomes="" attribute (that renames an element and
> therefore forgoes its semantics) but rather a way to get complete
> control over a semantic element and tweak aspects of it. Otherwise
> creating such controls is prohibiti
On 9/2/2011 6:39 PM, Alex Russell wrote:
Similarly, WCAG is a series of principles for designing usable, high quality
applications.
ARIA presents a set of semantic roles that don't exist in HTML, and
for those, alignment with custom element implementations is
outstanding. Components that expres
On Fri, 02 Sep 2011 20:47:27 +0200, Dimitri Glazkov
wrote:
Fear 6: Accessibility. Accessibility! Accessibility!?
I contend that the Component Model does not make accessibility any
worse. And likely the opposite.
By allowing ATs to traverse into shadow subtrees, and ensuring that
the shadow su
On Fri, Sep 2, 2011 at 3:58 PM, Charles Pritchard wrote:
> On 9/2/11 3:00 PM, Alex Russell wrote:
>>
>> On Fri, Sep 2, 2011 at 1:40 PM, Charles Pritchard wrote:
>>
>>>
>>> On 9/2/11 12:10 PM, Alex Russell wrote:
>>>
Since Dimitri has already said everything I would, and better, I just
>
On 9/2/11 3:00 PM, Alex Russell wrote:
On Fri, Sep 2, 2011 at 1:40 PM, Charles Pritchard wrote:
On 9/2/11 12:10 PM, Alex Russell wrote:
Since Dimitri has already said everything I would, and better, I just
want to very quickly second his point about where we are today vs.
where we fe
On Fri, Sep 2, 2011 at 1:40 PM, Charles Pritchard wrote:
> On 9/2/11 12:10 PM, Alex Russell wrote:
>>
>> Since Dimitri has already said everything I would, and better, I just
>> want to very quickly second his point about where we are today vs.
>> where we fear we might be: non-trivial apps have *
On 9/2/11 12:10 PM, Alex Russell wrote:
Since Dimitri has already said everything I would, and better, I just
want to very quickly second his point about where we are today vs.
where we fear we might be: non-trivial apps have *already* given up on
HTML. Suggesting that there's an un-semantic futu
Since Dimitri has already said everything I would, and better, I just
want to very quickly second his point about where we are today vs.
where we fear we might be: non-trivial apps have *already* given up on
HTML. Suggesting that there's an un-semantic future that will be
*caused* by the component
On Fri, Sep 2, 2011 at 2:30 AM, Anne van Kesteren wrote:
> On Wed, 31 Aug 2011 19:29:28 +0200, Dimitri Glazkov
> wrote:
>>
>> To put it differently, you want to start with a well-known element in
>> markup, and, through the magic of computing, this element _becomes_
>> your component in the DOM t
On Wed, 31 Aug 2011 19:29:28 +0200, Dimitri Glazkov
wrote:
To put it differently, you want to start with a well-known element in
markup, and, through the magic of computing, this element _becomes_
your component in the DOM tree. In other words, the markup:
Weee!!
Becomes:
Weee!!
This does
On Wed, Aug 31, 2011 at 10:29 AM, Dimitri Glazkov wrote:
> I will write up the exact algorithm in a wiki shortly.
Here it is: http://wiki.whatwg.org/wiki/Component_Model_Progressive_Enhancement
:DG<
Splitting off to its own thread, because this deserves a good discussion.
On Wed, Aug 31, 2011 at 12:00 AM, Anne van Kesteren wrote:
> On Wed, 31 Aug 2011 07:33:16 +0200, Dominic Cooney
> wrote:
>>
>> Thanks for reading this far! These proposals aren't formal or
>> detailed. I would love to get
18 matches
Mail list logo
