You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This example creates two x-foos in a <template repeat>. On IE, the last x-foo is unbound. It seems like for the last element the insertedCallback which cancels the unbind was fired after asyncUnbindAll has already taken effect.
It's only a problem when you use <template repeat> to make custom elements.
The text was updated successfully, but these errors were encountered:
We need to verify if the insertedCallback is fired too late or not fired at all.
On IE, the Mutation Observers polyfill uses mutation events. It's my understanding that they are synchronous so it seems unlikely that there's an ordering issue and more likely that the event is not firing at all.
I verified that it is firing by adding an inserted callback on x-foo. It
comes after the unbindAll call.
On Jun 21, 2013 4:49 PM, "Steve Orvell" [email protected] wrote:
We need to verify if the insertedCallback is fired too late or not fired
at all.
On IE, the Mutation Observers polyfill uses mutation events. It's my
understanding that they are synchronous so it seems unlikely that there's
an ordering issue and more likely that the event is not firing at all.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/187#issuecomment-19846652
.
@sorvell
Gist: https://gist.github.com/morethanreal/5825813
This example creates two
x-foo
s in a<template repeat>
. On IE, the lastx-foo
is unbound. It seems like for the last element the insertedCallback which cancels the unbind was fired after asyncUnbindAll has already taken effect.It's only a problem when you use
<template repeat>
to make custom elements.The text was updated successfully, but these errors were encountered: