ifications are probably already available.
*From:* Mike Kamermans [mailto:niho...@gmail.com ]
*Sent:* Friday, April 5, 2013 4:51 AM
*To:* public-webapps@w3.org
*Subject:* [webcomponents] self-documenting component.html files
Hi all,
a short while back I'd been working on a web compon
On 4/5/13 2:57 PM, Mike Kamermans wrote:
The getter/setter incur virtually no overhead, being baked into JS at the
lowest possible level, compared to mutation observers, which are rather
heavy hitting things for notifying non-owner objects of changes.
For what it's worth, I welcome actual perfo
Mutation Events (or rather, mutation observers) when we have
Object.defineProperty getter/setters don't make the most sense. The
getter/setter incur virtually no overhead, being baked into JS at the
lowest possible level, compared to mutation observers, which are rather
heavy hitting things for not
On Fri, Apr 5, 2013 at 7:39 PM, Travis Leithead
wrote:
> By "we" do you mean Presto-now-Blink? I expect there's too much web compat
> risk to remove Mutation Events anytime soon from a browser implementation.
By we I mean at least Gecko (to be perfectly clear, I'm not employed
by Opera), and lik
On Fri, Apr 5, 2013 at 7:29 PM, Travis Leithead
wrote:
> For the attribute changes, you can use MutationObservers, unless you need to
> have the values updated synchronously, in which case, you can always
> fallback to Mutation Events or hook the relevant APIs with ES5
> defineProperty overrides…?
: Friday, April 5, 2013 11:38 AM
To: Travis Leithead
Cc: Mike Kamermans; public-webapps@w3.org
Subject: Re: [webcomponents] self-documenting component.html files
On Fri, Apr 5, 2013 at 7:29 PM, Travis Leithead
wrote:
> For the attribute changes, you can use MutationObservers, unless you
are
probably already available.
From: Mike Kamermans [mailto:niho...@gmail.com]
Sent: Friday, April 5, 2013 4:51 AM
To: public-webapps@w3.org
Subject: [webcomponents] self-documenting component.html files
Hi all,
a short while back I'd been working on a web components demo, with one r
Hi all,
a short while back I'd been working on a web components demo, with one
result being a components.html that also acted as its own documentation
(since as a components.html anything that isn't 'more components', script,
or element, gets ignored), which sparked a small discussion on how
self-
