- From: Ryosuke Niwa <notifications@github.com>
- Date: Mon, 29 Aug 2016 14:10:04 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
Received on Monday, 29 August 2016 21:10:54 UTC
> Another thing is that if Custom Element classes are registered after the elements already exist in DOM, then their `attributeChangedCallback` methods will not be fired with the initially set attribute values (if any). This is explicitly not the case in v1 API. We would always invoke `attributeChangedCallback` on every attribute including ones that were present at the time of upgrade. If that's not the case, then we need to file a spec bug and fix that. -- 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/558#issuecomment-243257357
Received on Monday, 29 August 2016 21:10:54 UTC