Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lingering dgrid-preload node in dgrid/OnDemandGrid+dgrid/Tree #1406

Open
davidwarren opened this issue Dec 26, 2017 · 2 comments
Open

Lingering dgrid-preload node in dgrid/OnDemandGrid+dgrid/Tree #1406

davidwarren opened this issue Dec 26, 2017 · 2 comments
Labels
Milestone

Comments

@davidwarren
Copy link

I am running dojo-release-13.0, dgrid 1.2.1, and dstore 1.1.2.

The control appears correct to begin with, but after expanding sufficient rows I am left with a large dgrid-preload node in place of the correct data. The issue appears in firefox 57.0.2 but not 52.5.1. I am unable to reproduct in any browser besides firefox. No errors appear in console log.

This appears similar to #161. I can't come up with a predictable way to trigger other than to aggressively expand rows and scroll wildly. I'm not getting an "unresponsive script" error. After the error occurs once scrolling in the control behaves erratically.

@davidwarren
Copy link
Author

Example screenshots:

dtree-glitch-1
dtree-glitch-2

@dylans dylans added the bug label Jan 5, 2018
@dylans dylans added this to the 1.2.1 milestone Jan 5, 2018
@davidwarren
Copy link
Author

I've managed to somewhat mitigate this bug by changing the deferred delete via setTimeout at OnDemandGrid.js line 824 to directly delete the trashBin node. I still have the lingering preload nodes, but the grid now fixes itself once you scroll around a bit.

My running theory is the new firefox prioritizes interactive events above timeouts, and events are coming in fast enough that it attempts to re-rez a node before the timeout can fire. The cleanup function looks side-effect-free at first glance, but any attempt to rez another node could fail because the DOM enforces uniqueness of the id.

My theory depends on whether or not the id uniqueness is enforced when a node is rezzed or when a node is added to the dom, and I don't know that answer to that.

@dylans dylans modified the milestones: 1.2.1, 1.2.2 Apr 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants