Closed
Bug 1592775
Opened 5 years ago
Closed 5 years ago
Replay's frame timeline jumps after clicking on the timeline
Categories
(Firefox :: Untriaged, enhancement)
Firefox
Untriaged
Tracking
()
RESOLVED
FIXED
Firefox 72
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: jarilvalenciano, Assigned: jarilvalenciano, NeedInfo)
Details
Attachments
(1 file, 1 obsolete file)
2.75 MB,
video/quicktime
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.90 Safari/537.36
Steps to reproduce:
- Enable Replay in the devtools settings.
- Go to http://todomvc.com/examples/backbone/.
- Create a log point on app-view.js line 110 with the value this.$input.val().
- Create three todo items in TodoMVC.
- Click on the second message marker in the Replay timeline.
- Try clicking on assorted points in the frame timeline.
Actual results:
The timeline marker moves to the clicked position, but afterwards, it moves back to a random location.
Expected results:
The timeline should move to the clicked position and stay there.
Pushed by jlaster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/723eb1f37393 Fix jumping behavior in frame timeline r=jlast
Comment 3•5 years ago
|
||
Backed out for debugger failure
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=273831074&repo=autoland&lineNumber=94
Backout: https://hg.mozilla.org/integration/autoland/rev/f6b52f7d704495e146a89cc8cb3bc7aee3091be7
Flags: needinfo?(jarilvalenciano)
Pushed by jlaster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5fe1e03dbfbc Fix jumping behavior in frame timeline
Comment 5•5 years ago
|
||
bugherder |
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
Updated•5 years ago
|
Assignee: nobody → jarilvalenciano
Updated•5 years ago
|
Attachment #9105392 -
Attachment is obsolete: true
Comment 6•5 years ago
|
||
bugherder landing |
You need to log in
before you can comment on or make changes to this bug.
Description
•