On Sat, Sep 3, 2011 at 4:31 AM, Anne van Kesteren ann...@opera.com wrote:
On Fri, 02 Sep 2011 20:47:27 +0200, Dimitri Glazkov dglaz...@chromium.org
wrote:
BTW, I really ought to put this fears list on the Wiki.
Yeah that would probably be a good idea.
Done:
On Sun, Sep 4, 2011 at 1:56 PM, Dimitri Glazkov dglaz...@chromium.orgwrote:
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
On 3/09/11 4:47 AM, Dimitri Glazkov wrote:
On Fri, Sep 2, 2011 at 2:30 AM, Anne van Kesterenann...@opera.com wrote:
Examples of elements that should not be replaced but could be changed by a
binding: Having a sortable binding fortable; Exposing cite= on
blockquote; Turning aselect listing
On Fri, 02 Sep 2011 20:47:27 +0200, Dimitri Glazkov
dglaz...@chromium.org 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
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
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 prohibitively
On Sat, Sep 3, 2011 at 12:08 PM, Ian Hickson i...@hixie.ch 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
On Wed, 31 Aug 2011 19:29:28 +0200, Dimitri Glazkov
dglaz...@chromium.org 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:
button
On Fri, Sep 2, 2011 at 2:30 AM, Anne van Kesteren ann...@opera.com wrote:
On Wed, 31 Aug 2011 19:29:28 +0200, Dimitri Glazkov dglaz...@chromium.org
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_
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 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
On 9/2/11 3:00 PM, Alex Russell wrote:
On Fri, Sep 2, 2011 at 1:40 PM, Charles Pritchardch...@jumis.com 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
On Fri, Sep 2, 2011 at 3:58 PM, Charles Pritchard ch...@jumis.com wrote:
On 9/2/11 3:00 PM, Alex Russell wrote:
On Fri, Sep 2, 2011 at 1:40 PM, Charles Pritchardch...@jumis.com wrote:
On 9/2/11 12:10 PM, Alex Russell wrote:
Since Dimitri has already said everything I would, and better, I
Splitting off to its own thread, because this deserves a good discussion.
On Wed, Aug 31, 2011 at 12:00 AM, Anne van Kesteren ann...@opera.com wrote:
On Wed, 31 Aug 2011 07:33:16 +0200, Dominic Cooney domin...@chromium.org
wrote:
Thanks for reading this far! These proposals aren't formal or
On Wed, Aug 31, 2011 at 10:29 AM, Dimitri Glazkov dglaz...@chromium.org 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
15 matches
Mail list logo
