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
Chrome is running into this now (TypeErrors in notifyPath calls that did not previously throw an error).
There seems to be some kind of race condition where, if multiple elements reference the same object via data binding, when that object is initially set in one element, a full path for one of that object's sub-sub-sub-properties is sent via notifyPath to another element that hasn't yet received the base object.
My first impression is that there is a name collision between the inner template binding [[model]] which is a row and the outer property model which is a list.
I tried to pinpoint the bug around Templatizer._forwardInstanceProp or Base.notifyPath but no luck so far.
It seems that there is annotation scoping issue in templates that is now revealed by the changes in 2007-kschaaf-key-disambiguate.
Sorry for the large example, I couldn't make it smaller.
If you click on the test button, there is an exception in the following function from notify-path.html
This is because
x-row
tag is being notified on the following path:model.#0.#1.key
.If you replace the inner repeat by:
the problem disappears.
This issue had no consequence before the #2007 fix because notifications on invalid paths were simply ignored.
The text was updated successfully, but these errors were encountered: