On Mon, 10 Oct 2011, Dirk Pranke wrote:
On Wed, Sep 28, 2011 at 4:52 PM, Ian Hickson i...@hixie.ch wrote:
If an author invents a new element, it doesn't matter what it inherits
from. It won't have fallback behaviour, it won't have semantics that
can be interpreted by search engines and
On Mon, 10 Oct 2011, Charles Pritchard wrote:
Will I be writing the following:
div is=button role=button
Hopefully not, on two counts:
First, you should reuse button if it's a button, as in:
button is=fancybutton
Secondly, I would presume whatever solution we use for shadow tree
Hi Julien,
Thanks a lot for your interest and feedback! If I understand your example
correctly, it is very similar to the time-zone selection example Hixie gave
on this mailing list. As it so happens, I just added that as a use case for
components at
On Mon, 10 Oct 2011, Jonas Sicking wrote:
This will however be non-trivial to implement in Gecko as our HTTP layer
does the cookie handling, but the CORS implementation is built on top of
the HTTP layer.
That's essentially the same reason the spec does it too. Cookie setting is
handled at
On Tue, Oct 11, 2011 at 04:58, Ian Hickson i...@hixie.ch wrote:
On Tue, 4 Oct 2011, Roland Steiner wrote: On a second note, what you
essentially seem to demand is swapping out
entire HTML sub-branches based on presentation.
It's not how I would describe it (I wouldn't expect the shadow
On 9/27/11 3:56 PM, ext Arthur Barstow wrote:
On September 27 a Last Call Working Draft of Web IDL was published:
http://www.w3.org/TR/2011/WD-WebIDL-20110927/
The deadline for comments is October 18 and all comments should be
sent to:
public-script-co...@w3.org
The comment tracking doc
On Mon, Oct 10, 2011 at 7:51 PM, Sean Hogan shogu...@westnet.com.au wrote:
On 24/09/11 7:16 AM, Adam Klein wrote:
- Is free of the faults of the existing Mutation Events mechanism
(enumerated in detail here:
http://lists.w3.org/Archives/Public/public-webapps/2011JulSep/0779.html)
A simpler
On Tue, 11 Oct 2011, Roland Steiner wrote:
On Tue, Oct 11, 2011 at 04:58, Ian Hickson i...@hixie.ch wrote:
On Tue, 4 Oct 2011, Roland Steiner wrote:
On a second note, what you essentially seem to demand is swapping
out entire HTML sub-branches based on presentation.
It's not how I
On Mon, Oct 10, 2011 at 4:55 PM, Erik Arvidsson a...@chromium.org wrote:
Splitting this up into two different things is great.
The specific meaning of splitting up is where the things get
interesting. As far as I understand Hixie's idea, the component (which
exposes API) and the binding (which
On Tue, Oct 11, 2011 at 10:01 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Mon, Oct 10, 2011 at 4:55 PM, Erik Arvidsson a...@chromium.org wrote:
Splitting this up into two different things is great.
The specific meaning of splitting up is where the things get
interesting. As far as I
On Tue, 11 Oct 2011, Dimitri Glazkov wrote:
On Mon, Oct 10, 2011 at 4:55 PM, Erik Arvidsson a...@chromium.org wrote:
Splitting this up into two different things is great.
The specific meaning of splitting up is where the things get
interesting. As far as I understand Hixie's idea, the
On Tue, 11 Oct 2011, Tab Atkins Jr. wrote:
On Tue, Oct 11, 2011 at 10:01 AM, Dimitri Glazkov dglaz...@chromium.org
wrote:
On Mon, Oct 10, 2011 at 4:55 PM, Erik Arvidsson a...@chromium.org wrote:
Splitting this up into two different things is great.
The specific meaning of splitting up
By splitting I meant (and I think Ian did as well) that we have
decorators that does not change the interface and then we have
components which can change the shadow tree and define a new interface
(API).
The decorators can be attached and detached at runtime using css and
maybe even an
On Tue, Oct 11, 2011 at 11:25 AM, Erik Arvidsson a...@chromium.org wrote:
By splitting I meant (and I think Ian did as well) that we have
decorators that does not change the interface and then we have
components which can change the shadow tree and define a new interface
(API).
The
On Tue, 11 Oct 2011, Dimitri Glazkov wrote:
On Tue, Oct 11, 2011 at 11:25 AM, Erik Arvidsson a...@chromium.org wrote:
By splitting I meant (and I think Ian did as well) that we have
decorators that does not change the interface and then we have
components which can change the shadow tree
Is there a comment tracking doc for this LC (e.g., lc2)?
-Original Message-
From: public-script-coord-requ...@w3.org [mailto:public-script-coord-
requ...@w3.org] On Behalf Of Arthur Barstow
Sent: Tuesday, October 11, 2011 4:37 AM
To: public-script-coord; public-webapps
Subject: Reminder:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13972
Art Barstow art.bars...@nokia.com changed:
What|Removed |Added
Status|NEW |RESOLVED
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14084
Art Barstow art.bars...@nokia.com changed:
What|Removed |Added
Status|NEW |RESOLVED
I'm not sure if you're on device-apis, Marcos, but you might be
interested in this - what happens when you no longer need to intercept
localhost;
http://www.w3.org/mid/6dfa1b20d858a14488a66d6eedf26aa35d61fed...@seldmbx03.corpusers.net
Mark.
On Tue, 11 Oct 2011, Erik Arvidsson wrote:
I think one thing that is missing from this table/proposal is how the
prototype chain is hooked up.
For the permanent case I would like to see the user defined object on
that chain.
script
function FancyButton () {}
// registration and whatevs
On 10/11/11 4:08 PM, ext Travis Leithead wrote:
Is there a comment tracking doc for this LC (e.g., lc2)?
I don't see one in CVS. (I think Cameron returns soon though.)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14084
Anne ann...@opera.com changed:
What|Removed |Added
Resolution|LATER |WONTFIX
--- Comment #5 from
Hi all,
To give a broader overview over the everything involved with components, I
summarized all open questions (as far as we see it) at
http://wiki.whatwg.org/wiki/Component_Model_Discussion .
Please chime in with opinions on any item and/or stuff you think is missing
and should belong on the
23 matches
Mail list logo
