Brendan Baldwin
Brendan Baldwin
Okay I should have it a method for it in the next patch release. We are still getting trying to usher the next batch of package releases in the lit...
Wanted to clarify that there are 3 scenarios here as I am adding support methods to suppress this annoying error. The scenario that has mattered the most generally has been...
#3929 should resolve the first case window.onerror (test frameworks like Mocha etc) and provides an addEventListener option for second case.
@akc42 let me know if these functions added helped you out. I'll be looking at ways to reduce the cascade of observer callbacks architecture-wise following an upcoming big refactor that...
Thanks for filing this. We have no tests around a virtualizer in a display:none case! Your workaround sounds like the right one for now but we'll see if there might...
#3835 updates README
I switched to Atom from Emacs a little while ago and am never going back, so I +1 the value of supporting Atom. Seems potentially even easier than supporting Sublime...
I think the solution may be to change the code in cell 4 which does not set args.scene_start and args.scene_end in the animatediff case: ```python for scene in filtered_scenes: if...
for what it's worth, this does fix this problem, but i almost always immediately bump into a problem with either batch or context size exceeding scene size with animatediff and...
FWIW, in the virtualizer tests for now, I am essentially using `await until(() => /* eventually expected state */)` instead of `await el.updateComplete`