Re: [w3c/webcomponents] DOM APIs which replace all children end up firing superfluous slotchange events (#764) from Hayato Ito on 2018-08-31 (public-webapps-github@w3.org from August 2018)

From: Hayato Ito <notifications@github.com>
Date: Fri, 31 Aug 2018 00:01:05 -0700
To: w3c/webcomponents <webcomponents@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <w3c/webcomponents/issues/764/417571748@github.com>

It looks an expected behavior to me; Fire slotchange events on every slots if their assigned nodes are changed.

I wonder what is a practical issue for the current expected behavior? Could you share that with us?

Unless there is a strong practical issue, I would prefer a consistent behavior.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/764#issuecomment-417571748

Received on Friday, 31 August 2018 07:01:27 UTC