Reproducing & debugging this locally didn't bring news, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
The next 10 reattempts have the same output.
Bug 1554964 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Reproducing & debugging this locally didn't bring something new, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
The next 10 reattempts have the same output.
Reproducing & debugging this locally didn't bring something new, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
Once this happens, the next 10 reattempts have the same output.
Reproducing & debugging this locally didn't bring something new, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
Once this happens, the next 10 reattempts have the same output and then the test officially times out.
Reproducing & debugging this locally didn't bring something new, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
Once this happens, the next 10 reattempts have the same output and then the test officially times out & notifies the control server.
Reproducing & debugging this locally didn't bring something new, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
Once this happens, the next 10 reattempts become useless. They have the same output and then the test officially times out & notifies the control server.
Reproducing & debugging this locally didn't bring something new, expect that at some point `window.performance.getEntriesByType("paint")` returns an empty array.
Once this happens, the next 10 reattempts become useless. They produce the same output and then the test officially times out & notifies the control server.