This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Bugfix: run AppInit._dispatchReady AFTER loading the extensions #1854
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ghost
assigned 
|
Yikes. Thanks for catching that. Merging. |
jasonsanjose
added a commit
that referenced
this pull request
Oct 16, 2012
Bugfix: run AppInit._dispatchReady AFTER loading the extensions
|
To clarify the situation with #1526 (per Dennis's notes there): APP_READY is still not guaranteed to fire after the initial document is loaded. It was a race condition before, and remains a race condition after this patch -- it's now somewhat more likely that APP_READY happens second, but depending on timing sometimes it could still come first. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This restores the intended behavior of what once was
brackets.ready.It could therefore be considered a fix for #1526, but please note the comments there.