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 Mon, 29 Aug 2011, Philippe Le Hegaret wrote:
But, the WHATWG HTML links to the editor's drafts and does not link to
the TR one. While documents on the REC-track should link to other
documents on the REC tracks, this doesn't apply to editor's draft, which
have no special status anyway.
On Tue, 30 Aug 2011, Dominic Cooney wrote:
I'm proposing we add something that lets script extend the set of tag
names, so there is less of a bright line between elements defined in the
HTML spec and elements defined in script. Something like:
HTMLElement.register('x-contacts',
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 Thu, 1 Sep 2011, Jonas Sicking wrote:
1. It doesn't allow receiving textual messages as Blobs, only binary
messages can be stored as blobs.
Huh. I never considered that people might want to have the server send
stuff as text but still want to treat it as a Blob on the receiving side.
On Saturday, 3 September 2011 at 20:54, Ian Hickson wrote:
On Mon, 29 Aug 2011, Philippe Le Hegaret wrote:
But, the WHATWG HTML links to the editor's drafts and does not link to
the TR one. While documents on the REC-track should link to other
documents on the REC tracks, this
Hi Dom,
Thank you for continuing to keep the document up to date. This document is very
helpful.
I have request: can you please ungroup Widgets and HTML's ApplicationCache?
They are conceptually different things and have different use cases.
Widgets are a way to zip up a bunch of HTML,
On Sat, Sep 3, 2011 at 12:04 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 30 Aug 2011, Dominic Cooney wrote:
I'm proposing we add something that lets script extend the set of tag
names, so there is less of a bright line between elements defined in the
HTML spec and elements defined in script.
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 Sat, 3 Sep 2011, Dominic Cooney wrote:
I think the XBL approach is far superior here -- have authors use
existing elements, and use XBL to augment them. For example, if you
want the user to select a country from a map, you can use a select
with a list of countries in option
Be careful with the big words. It can't be that inferior if it
satisfies use cases that XBL2 can't.
:DG
On Sat, Sep 3, 2011 at 8:20 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 3 Sep 2011, Dominic Cooney wrote:
I think the XBL approach is far superior here -- have authors use
existing
On Sat, Sep 3, 2011 at 8:20 PM, Ian Hickson i...@hixie.ch wrote:
On Sat, 3 Sep 2011, Dominic Cooney wrote:
I think the XBL approach is far superior here -- have authors use
existing elements, and use XBL to augment them. For example, if you
want the user to select a country from a map,
13 matches
Mail list logo
