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
{{ message }}
Repository navigation
chore(context): disposal-time 'batched listener threw DOMException' warn during _disposeTree #325
Observed as pre-existing console.warn noise while running tests/directives-http-pagination.test.js test 70 (dispose mid-defer): context.js:~53 defensive catch logs 'batched listener threw DOMException' when a batched watcher fires against an already-disposed tree. Not user-visible breakage, but it means a watcher survives into disposal long enough to throw. Investigate whether a disposal-order guard (skip notify for disposed contexts) removes the noise; keep the defensive catch either way.
Another reproduction of a watcher surviving into a stale tree, found during the 1.22 docs runtime sweep: an each inside a get that first shows its error template and then succeeds on refresh() (or a URL change) logs batched listener threw … insertBefore. The list still renders correctly, which points to the each watcher from the pre-error render not being disposed when the content is swapped.
Activity
ErickXavier commentedon Oct 22, 2026
Another reproduction of a watcher surviving into a stale tree, found during the 1.22 docs runtime sweep: an
eachinside agetthat first shows itserrortemplate and then succeeds onrefresh()(or a URL change) logsbatched listener threw … insertBefore. The list still renders correctly, which points to theeachwatcher from the pre-error render not being disposed when the content is swapped.