I think the problem here is not specific to web replay: when the server has paused at a location within a blackboxed source, it has trouble stepping forward whether web replay is turned on or not. I can't reproduce this specific STR without web replay because message warping is only supported with web replay on, but here are similar STR without web replay is as follows: 1. go to https://firefox-dev.tools/debugger-examples/examples/todomvc/ 2. set a breakpoint at the start of logTodo in log.js 3. edit a todo, so that the debugger pauses at the breakpoint 4. blackbox log.js 5. press step over The process then resumes, when it seems better that it should step out to the first non-blackboxed frame. Fixing this in the non-web-replay case will probably fix the web replay case as well.
Bug 1575071 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I think the problem here is not specific to web replay: when the server has paused at a location within a blackboxed source, it has trouble stepping forward whether web replay is turned on or not. I can't reproduce this specific STR without web replay because message warping is only supported with web replay on, but here are similar STR without web replay: 1. go to https://firefox-dev.tools/debugger-examples/examples/todomvc/ 2. set a breakpoint at the start of logTodo in log.js 3. edit a todo, so that the debugger pauses at the breakpoint 4. blackbox log.js 5. press step over The process then resumes, when it seems better that it should step out to the first non-blackboxed frame. Fixing this in the non-web-replay case will probably fix the web replay case as well.