Auto-Submit | +1 |
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Code-Review | +1 |
Just nits and observations...
// 1.pointerdown, 2. pointerup, 3. click
nit: Missing period at the end. :)
// 1.pointerdown, 2. pointerup, 3. click
nit: missing space after period.
// 1.pointerdown, 2. pointerup, 3. click
Looks like the test expectations have changed, but the comment is documenting the old way, not the new way...
nit: Is this intentional? Don't care much either way, just thought I'd ask.
assert.strictEqual(keyboardInteraction.mainThreadHandling, 143901);
Just an observation... this variable name (mainThreadHandling) is not a very descriptive one, for a duration... (beyond the scope for this CL though)
// end events were used which meant the durations of the interaction events
micro-not: comma before 'which'.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Auto-Submit | +1 |
Commit-Queue | +2 |
nit: missing space after period.
Done
Looks like the test expectations have changed, but the comment is documenting the old way, not the new way...
Done
nit: Missing period at the end. :)
Done
// 4. keydown, 5. keyup
Jack Franklinditto. :)
Done
assert.strictEqual(keyboardInteraction.mainThreadHandling, 143901);
Just an observation... this variable name (mainThreadHandling) is not a very descriptive one, for a duration... (beyond the scope for this CL though)
Yeah, I would agree. I will send another CL to rename. I'd probably just lob `Duration` on the end. wdyt?
// end events were used which meant the durations of the interaction events
micro-not: comma before 'which'.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
2 is the latest approved patch-set.
The change was submitted with unreviewed changes in the following files:
```
The name of the file: front_end/models/trace/handlers/UserInteractionsHandler.test.ts
Insertions: 3, Deletions: 3.
The diff is too large to show. Please review the diff.
```
RPP: fix incorrect Interactions timeline
This is the same fix as crrev.com/c/6969008 but applied to the
UserInteractionsHandler, which does not use our generic event pairing
implementation (it should, but it works slightly differently with how we
construct the events, so I will tackle that in a separate CL).
Perfetto changed to reuse IDs for non-overlapping event pairs, and the
UserInteractionsHandler did not account for this. This CL ensures that
it does, meaning that we no longer pair events inaccurately in the
timeline.
Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |