forked from davidtodd/landmarks
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Bootstrapping readyState checks not necessary #137
Comments
The following code and translation messages should be removable then:
|
matatk
added a commit
that referenced
this issue
Jan 12, 2018
* Remove unused translation message. * Simplify LandmarksFinder API and rename functions for clarity (they are getters). This fixes a bug that was there for ages whereby it was not calling the function to check the number of landmarks found (in checkFocusElement()). * Vastly simplify the bootstrapping code in content.overall.js. * Move Logger to content.overall.js from content.pausing.js and generalise. * Remove Logger from content.pausing.js.
matatk
added a commit
that referenced
this issue
Jan 12, 2018
* Remove unused translation message. * Simplify LandmarksFinder API and rename functions for clarity (they are getters). This fixes a bug that was there for ages whereby it was not calling the function to check the number of landmarks found (in checkFocusElement()). * Vastly simplify the bootstrapping code in content.overall.js. * Move Logger to content.overall.js from content.pausing.js and generalise. * Remove Logger from content.pausing.js. * Disconnect observer if content script has been retired (fixes #131).
matatk
added a commit
that referenced
this issue
Jan 18, 2018
* Remove unused translation message. * Simplify LandmarksFinder API and rename functions for clarity (they are getters). This fixes a bug that was there for ages whereby it was not calling the function to check the number of landmarks found (in checkFocusElement()). * Vastly simplify the bootstrapping code in content.overall.js. * Move Logger to content.overall.js from content.pausing.js and generalise. * Remove Logger from content.pausing.js. * Disconnect observer if content script has been retired (fixes #131).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Both the Chrome developer docs and the MDN docs state that the DOM will be complete when "document_idle" content scripts are run (which is the default).
Therefore, the whole
bootstrap()
readyState
-checking stuff can be removed.Will add some temporary logging in case the completion of loading of any assets does affect mutations.
The text was updated successfully, but these errors were encountered: