Andrés Olivares 8226242ba4 Do not trigger track update if selected track has not changed ...

This avoids unnecessary work in the load of the panel. See the
screenshots that show that 3 track updates are done on every trace load.
Interestingly enough, we don't need to do that many.

Before: https://screenshot.googleplex.com/8Y7c4jWbnWnqoyU
After: https://screenshot.googleplex.com/8zLxtnkkYTBTkFz

Bug: 1472155
Change-Id: I038b2add48342e4e7d83d694136c8d3d76712f44
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/4935530
Reviewed-by: Nancy Li <nancyly@chromium.org>
Commit-Queue: Andres Olivares <andoli@chromium.org>
Commit-Queue: Nancy Li <nancyly@chromium.org>
Auto-Submit: Andres Olivares <andoli@chromium.org>

2023-10-13 10:01:45 +00:00

..

wasm

Update puppeteer and @puppeteer/replay

2023-06-26 18:05:57 +00:00

BUILD.gn

Migrate the timeline-js-line-level-profile-no-url-end-to-end_test test

2023-03-28 11:29:30 +00:00

emulate-hardware-concurrency_test.ts

Add a tooltip text for the hardware concurrency override setting

2023-06-30 15:08:06 +00:00

recording_test.ts

Do not trigger track update if selected track has not changed

2023-10-13 10:01:45 +00:00

settings-throttle-persist_test.ts

Update puppeteer and @puppeteer/replay

2023-06-26 18:05:57 +00:00

timeline-js-line-level-profile-no-url-end-to-end_test.ts

Update puppeteer and @puppeteer/replay

2023-06-26 18:05:57 +00:00