Skip to content

Conversation

@nicholasray
Copy link
Contributor

@nicholasray nicholasray commented Oct 7, 2022

jsReady.js and moduleReady.js effectively wait for various JS resource loader modules to load which can be tedious to write and error prone. There might be a better and more future-proof alternative by waiting for the network to idle instead.

Therefore, this commit:

  • Replaces all usages of waitForModule with waitForNetworkIdle
  • Removes moduleReady.js and jsReady.js

@nicholasray nicholasray marked this pull request as draft October 7, 2022 22:13
@nicholasray nicholasray changed the title Remove jsReady.js Replace jsReady.js with waitForNetworkIdle Oct 7, 2022
@nicholasray nicholasray force-pushed the remove-js-ready branch 3 times, most recently from 88924cd to b571827 Compare November 4, 2022 20:13
@nicholasray nicholasray changed the title Replace jsReady.js with waitForNetworkIdle Replace jsReady.js and moduleReady.js with waitForNetworkIdle call Nov 4, 2022
@nicholasray nicholasray force-pushed the remove-js-ready branch 3 times, most recently from 3bd1ac0 to 2252a30 Compare November 4, 2022 20:26
@nicholasray nicholasray marked this pull request as ready for review November 4, 2022 21:00
jsReady.js and moduleReady.js effectively wait for various JS resource loader
modules to load which can be tedious to write and error prone. There might be a
better and more future-proof alternative by waiting for the network to idle
instead.

Therefore, this commit:

* Replaces all usages of waitForModule with waitForNetworkIdle
* Removes moduleReady.js and jsReady.js

Bug: T322454
@nicholasray nicholasray marked this pull request as draft November 4, 2022 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant