Re: TPAC Topic: Using ES2015 Modules in HTML

Consider this a second vote for a California-compatible time for such a discussion. V8 also has a partial ES2015 module implementation that's blocked on the loader, and I'm very interested in pushing forward support for modules in HTML. On Fri, Oct 16, 2015 at 5:39 AM, Ryosuke Niwa wrote: > Hi a

Re: Writing spec algorithms in ES6?

On Thu, Jun 11, 2015 at 1:32 PM, Dimitri Glazkov wrote: > Folks, > > Many specs nowadays opt for a more imperative method of expressing > normative requirements, and using algorithms. For example, both HTML and > DOM spec do the "run following steps" list that looks a lot like > pseudocode, and t

Re: Custom Elements: insert/remove callbacks

On Thu, May 7, 2015 at 10:56 PM, Elliott Sprehn wrote: > > On Thu, May 7, 2015 at 10:44 PM, Anne van Kesteren > wrote: > >> On Fri, May 8, 2015 at 7:42 AM, Elliott Sprehn >> wrote: >> > That actually seems pretty similar to what we have, ours is in the form >> of: >> > >> > Node#insertedInto(No

Re: Privileged context features and JavaScript

On Fri, Apr 17, 2015 at 7:06 AM, Boris Zbarsky wrote: > On 4/17/15 3:38 AM, Elliott Sprehn wrote: > >> It's preferable not to do that for us because you can then create a >> static heap snapshot at compile time and memcpy to start JS contexts >> faster. >> > > For this specific case, where there

Re: template namespace attribute proposal

On Thu, Mar 12, 2015 at 11:22 AM, Anne van Kesteren wrote: > On Thu, Mar 12, 2015 at 7:16 PM, Adam Klein wrote: > > For clarity, is this significantly different from the below (which works > > today)? > > > > > > > > > > > >

Re: template namespace attribute proposal

On Wed, Mar 11, 2015 at 8:32 PM, Benjamin Lesh wrote: > I'd like to propose that the tag have a namespace="" attribute > that allows the user to specify namespaces such as " > http://www.w3.org/2000/svg";, so that the document fragment that comes > from `.content` is created properly. > > e.g.:

Re: Custom element lifecycle callbacks

On Thu, Jan 8, 2015 at 7:56 AM, Anne van Kesteren wrote: > 1) Can we use symbols to identify these instead? That gives us a > guarantee they won't be used for other things and makes it somewhat > safer to put them where they are located now. > As Dimitri noted, I've expressed mild concerns about

Re: Indexed DB Transactions vs. Microtasks

On Fri, Jun 6, 2014 at 5:51 PM, Jonas Sicking wrote: > On Thu, Jun 5, 2014 at 12:59 PM, Joshua Bell wrote: > > case 1: > > > > var tx; > > Promise.resolve().then(function() { > > tx = db.transaction(storeName); > > // tx should be active here... > > }).then(function() { > > //

Re: Indexed DB Transactions vs. Microtasks

On Wed, Jun 18, 2014 at 9:13 PM, Domenic Denicola < dome...@domenicdenicola.com> wrote: > [+Yehuda, +Raf] > > From: Jonas Sicking [mailto:jo...@sicking.cc] > > > On Thu, Jun 19, 2014 at 8:44 AM, Adam Klein wrote: > >> While I agree that the original microtask in

Re: Indexed DB Transactions vs. Microtasks

On Fri, Jun 6, 2014 at 5:51 PM, Jonas Sicking wrote: > On Thu, Jun 5, 2014 at 12:59 PM, Joshua Bell wrote: > > case 1: > > > > var tx; > > Promise.resolve().then(function() { > > tx = db.transaction(storeName); > > // tx should be active here... > > }).then(function() { > > //

Re: Why can't we just use constructor instead of createdCallback?

On Tue, Feb 18, 2014 at 3:26 PM, Dimitri Glazkov wrote: > On Tue, Feb 18, 2014 at 2:59 PM, Jonas Sicking wrote: > > On Tue, Feb 18, 2014 at 10:35 AM, Dimitri Glazkov > > wrote: > > > The thing that really bothers me is that this approach is contradicting > > > itself. We go to into pretty elabo

Re: Making play nice with XML and tags-and-text

On Wed, Jul 18, 2012 at 9:19 AM, Adam Barth wrote: > Inspired by a conversation with hsivonen in #whatwg, I spend some time > thinking about how we would design for an XML world. One idea I > had was to put the elements inside the template into a namespace other than > http://www.w3.org/1999/xh

Re: Should MutationObservers be able to observe work done by the HTML parser?

On Fri, Jun 29, 2012 at 2:44 AM, Jonas Sicking wrote: > All in all I think that as soon as we introduce exceptions to when > MutationObserver callbacks fire we change the API from being a > reliable way to track DOM mutations to a unreliable way where all > callers have to be aware of exceptions

Re: Should MutationObservers be able to observe work done by the HTML parser?

On Wed, Jun 20, 2012 at 12:29 AM, Anne van Kesteren wrote: > On Tue, Jun 19, 2012 at 10:52 PM, Olli Pettay > wrote: > > end-of-microtask or end-of-task everywhere. And yes, some parsing / > > networking details may unfortunately be exposed, > > but in a way which should be quite random. Web devs

Re: Should MutationObservers be able to observe work done by the HTML parser?

On Wed, Jun 20, 2012 at 12:36 AM, Ryosuke Niwa wrote: > On Tue, Jun 19, 2012 at 1:52 PM, Olli Pettay wrote: >> >> Ojan points out >> >>> that simply using end-of-task could expose low-level implementation >>> detail of the parser to script (such as how much parsing is done in a >>> single task

Re: Should MutationObservers be able to observe work done by the HTML parser?

On Sun, Jun 17, 2012 at 12:17 PM, Ryosuke Niwa wrote: > On Sun, Jun 17, 2012 at 5:03 AM, Jonas Sicking wrote: > >> On Sat, Jun 16, 2012 at 7:04 AM, Rafael Weinstein >> wrote: >> > I too thought we had intentionally spec'd them to not fire during load. >> > >> > The HTML spec is clear about this

Re: [DOM4] NodeList should be deprecated

On Thu, Mar 8, 2012 at 11:57 PM, Anne van Kesteren wrote: > On Thu, 08 Mar 2012 23:24:45 +0100, Ojan Vafai wrote: > >> Dynamic NodeLists have a significant memory and performance cost. Static >> NodeLists are basically just under-powered arrays. We should just return >> Node arrays from any new

Re: Mutation Observers: a replacement for DOM Mutation Events

On Fri, Sep 30, 2011 at 7:03 PM, Ojan Vafai wrote: > On Fri, Sep 30, 2011 at 12:40 PM, Ms2ger wrote: >> >> On 09/29/2011 04:32 PM, Doug Schepers wrote: >>> >>> Hi, Adam- >>> >>> I'm glad to see some progress on a replacement for Mutation Events. >>> >>> Would you be interested in being the editor

Re: Mutation Observers: a replacement for DOM Mutation Events

On Tue, Sep 27, 2011 at 1:12 PM, Olli Pettay wrote: > On 09/24/2011 12:16 AM, Adam Klein wrote: >> >> For each observer, if a registration exists which requests the >> matching mutation type and whose observed node set contains the target >> node of the mutation, a Mu

Re: Mutation Observers: a replacement for DOM Mutation Events

On Mon, Sep 26, 2011 at 12:08 PM, Olli Pettay wrote: > On 09/26/2011 09:09 PM, Adam Klein wrote: >> >> On Mon, Sep 26, 2011 at 11:05 AM, Olli Pettay >>  wrote: >>> >>> On 09/24/2011 12:16 AM, Adam Klein wrote: >>>> >>>> Chromi

Re: Mutation Observers: a replacement for DOM Mutation Events

On Mon, Sep 26, 2011 at 1:47 AM, Olli Pettay wrote: > On 09/24/2011 12:16 AM, Adam Klein wrote: >> >> Chromium (myself, Rafael Weinstein, Erik Arvidsson, Ryosuke Niwa) and >> Mozilla (Olli Pettay, Jonas Sicking) have worked together on a >> proposal for a repl

Re: Mutation Observers: a replacement for DOM Mutation Events

On Mon, Sep 26, 2011 at 11:05 AM, Olli Pettay wrote: > On 09/24/2011 12:16 AM, Adam Klein wrote: >> >> Chromium (myself, Rafael Weinstein, Erik Arvidsson, Ryosuke Niwa) and >> Mozilla (Olli Pettay, Jonas Sicking) have worked together on a >> proposal for a repl

Re: Mutation Observers: a replacement for DOM Mutation Events

On Fri, Sep 23, 2011 at 4:44 PM, Tab Atkins Jr. wrote: > On Fri, Sep 23, 2011 at 2:16 PM, Adam Klein wrote: >> [Constructor(in MutationCallback callback)] >> interface MutationObserver { >>   void observe(in Node target, in MutationObserverOptions options); >>   void

Mutation Observers: a replacement for DOM Mutation Events

Chromium (myself, Rafael Weinstein, Erik Arvidsson, Ryosuke Niwa) and Mozilla (Olli Pettay, Jonas Sicking) have worked together on a proposal for a replacement for Mutation Events. This proposal represents our best attempt to date at making a set of sensible trade offs which allows for a new mutat

Re: Mutation events replacement

On Thu, Jul 21, 2011 at 4:30 PM, Jonas Sicking wrote: > On Thu, Jul 21, 2011 at 8:19 AM, Olli Pettay wrote: >> On 07/21/2011 06:01 PM, Boris Zbarsky wrote: >>> >>> On 7/21/11 5:08 AM, Dave Raggett wrote: Thanks for the explanation. Apps would need a way to disable notifications dur

Re: Mutation events replacement

On Mon, Jul 4, 2011 at 1:45 PM, Olli Pettay wrote: > On 07/04/2011 08:16 PM, Adam Klein wrote: >> On Mon, Jul 4, 2011 at 9:57 AM, Olli Pettay >>  wrote: >>> On 07/04/2011 07:28 PM, Ojan Vafai wrote: >>>> The only bit that might be slower is what data you

Re: Mutation events replacement

On Mon, Jul 4, 2011 at 9:57 AM, Olli Pettay wrote: > On 07/04/2011 07:28 PM, Ojan Vafai wrote: >> >> Apologies in advance if my comment makes no sense. This is a long >> thread, I tried to digest it all. :) >> >> On Sat, Jul 2, 2011 at 7:07 AM, Boris Zbarsky > > wrote: >>