DEV: Improve built-in browser performance marks/measurements #26758
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.
Rename
discourse-booted
to 'discourse-init' (because 'booted' makes it sound like boot was finished. When in fact, it was just starting)Introduce
discourse-paint
, which is fired after the Ember application has been painted to the screen by the browser. This happens slightly after DOMContentLoadedAdd a
performance.measure
call to link those two marks, so they're easily visible in performance tracesAlso removes an ember boot-order workaround which is no longer required.