W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2015

Re: Imperative API for Node Distribution in Shadow DOM (Revisited)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 30 Apr 2015 15:22:21 +0200
Message-ID: <CADnb78ik=Cyegn7t9=PmDAJUwsskCsOQX0SUENgiiwcJNaTrCQ@mail.gmail.com>
To: Hayato Ito <hayato@chromium.org>
Cc: Domenic Denicola <d@domenic.me>, Ryosuke Niwa <rniwa@apple.com>, Justin Fagnani <justinfagnani@google.com>, WebApps WG <public-webapps@w3.org>, Erik Bryn <erik@erikbryn.com>, Dimitri Glazkov <dglazkov@google.com>, "Edward O'Connor" <eoconnor@apple.com>, Steve Orvell <sorvell@google.com>
On Thu, Apr 30, 2015 at 3:05 PM, Hayato Ito <hayato@chromium.org> wrote:
> That's the exactly intended behavior in the current spec.
> The timing of distribution is not observable.

Right, but you can synchronously observe whether something is
distributed. The combination of those two things coupled with us not
wanting to introduce new synchronous mutation observers is what
creates problems for an imperative API.

So if we want an imperative API we need to make a tradeoff. Do we care
about offsetTop et al or do we care about microtask-based mutation
observers? I'm inclined to think we care more about the latter, but
the gist I put forward takes a position on neither and leaves it up to
web developers when they want to distribute (if at all).

Received on Thursday, 30 April 2015 13:22:47 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:27:31 UTC