[custom-elements] Invoking lifecycle callbacks before invoking author scripts

2016-02-22 Thread Ryosuke Niwa
Hi, We propose to change the lifecycle callback to be fired both before invoking author scripts (e.g. for dispatching events) and before returning to author scripts. Without this change, event listeners that call custom elements' methods would end up seeing inconsistent states during compound

Re: TPAC 2016 - meetings

2016-02-22 Thread Ryosuke Niwa
I'd like to attend Web Perf WG's meeting so it would be ideal if any meetings held for Web Apps WG didn't overlap with those of Web Perf WG's. > On Feb 10, 2016, at 4:34 AM, Chaals McCathie Nevile > wrote: > > Dear all, > > as you probably know, the W3C will hold its

Re: File API - where are the missing parts?

2016-02-22 Thread Jonas Sicking
On Sun, Feb 21, 2016 at 3:32 AM, Florian Bösch wrote: > > *What this covers* > >- Read one or many files in their entirety in one go (in python that >would be open('foobar').read()) >- Save a completed binary string in its entirety in one go to the >download

Re: [ServiceWorker] Expose GeoLocation to workers (#745)

2016-02-22 Thread Richard Maher
I found a very interesting, and inspiring quote today that I'd like to share with you: - https://twitter.com/jaffathecake Googler. "I want the web to do everything native can, and fast." So can anyone here explain to me how that precludes device/user tracking? Or how HTML5 Web Apps can not be

[custom-elements] Steps inside HTMLElement's constructor

2016-02-22 Thread Ryosuke Niwa
Hi all, Here are steps to construct a custom element as agreed during Jan F2F as I promised to write down [1] [2]: Modify http://w3c.github.io/webcomponents/spec/custom/#dfn-element-definition as follows: The element definition describes a custom element and consists of: * custom element

Re: [custom-elements] Steps inside HTMLElement's constructor

2016-02-22 Thread Ryosuke Niwa
> On Feb 22, 2016, at 10:46 PM, Ryosuke Niwa wrote: > > Here are steps to construct a custom element as agreed during Jan F2F as I > promised to write down [1] [2]: There's a very appealing alternative to this, which doesn't involve having a element construction stack per