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

Already on GitHub? Sign in to your account

Navigator highlight does not always find new resource DOM nodes after a full navigator reload #246

nierajsingh opened this Issue Feb 27, 2013 · 0 comments


None yet
1 participant

nierajsingh commented Feb 27, 2013

Sometimes when attempting to highlight a new resource in the navigator, for example a newly created or renamed file, after an explorer reload, the postOperation performed after reload, if implemented to attempt to perform a navigator highlight, will still not find the new elements in the document. Setting a setTimeout temporarily serves as a workaround, but a better solution is to wait for the document to be ready before attempting to check for the new element nodes. This is a case in contextmenuprovider.js that uses a setTimeout. This should be replaced with a better solution.

@ghost ghost assigned nierajsingh Feb 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment