Update Async Stack UI
Categories
(DevTools :: Debugger, enhancement)
Tracking
(firefox75 fixed)
| Tracking | Status | |
|---|---|---|
| firefox75 | --- | fixed |
People
(Reporter: jlast, Assigned: jlast)
References
Details
Attachments
(1 file)
Now that we show captured frames, we should update the look and feel to show async causes as separators
| Assignee | ||
Comment 1•6 years ago
|
||
Updated•6 years ago
|
Comment 3•6 years ago
|
||
:jlast, I've noticed that this changeset was landed without the reviewer, can you please make sure to get patches landed properly in the future (e.g. with reviewer and author of the landed code different)? Thank you!
Comment 4•6 years ago
|
||
That's on me, I accepted the revision but there was one small linter failure. Instead of waiting for Jason, I commandeered the patch and fixed the lint failure and landed it all.
It looks like when I commandeered the revision, it cleared the review state and I couldn't mark it as reviewed because it was now owned by me.
Comment 5•6 years ago
|
||
| bugherder | ||
Comment 6•6 years ago
|
||
Thank you Logan for your input and clarifications!
Comment 7•6 years ago
|
||
@Cristian Is there anything I should have done differently here, or something that could be changed in the Phabricator workflow to avoid confusion like this? For instance, if I were able to push a small change to the patch without commandeering, we could avoid this confusion, or if Phabricator hadn't automatically changed the reviewer to Jason and cleared the review state when I commandeered the patch.
Comment 8•6 years ago
|
||
I think that Aryx can fully answer your question here, ty.
Comment 9•6 years ago
|
||
From recent observations, in general the patch author addresses the review comments and pushes. What could have done is to pick "Edit Revision" in Phabricator and edit the commit message there to add r=you.
Updated•4 years ago
|
Description
•