* SUMMARY Timeline's Current Time does not jump forward to new start time when starting a new recording, causes timeline to appear delayed and broken. * STEPS TO REPRODUCE 1. Inspect https://en.wikipedia.org/wiki/Main_Page 2. Show timelines tab 3. Command-R to reload 4. Timeline starts automatically 5. Wait for timeline to stop or manually stop at about the 5s mark. 6. Wait 30 seconds 7. Click button to start recording 8. Scroll page a bit to ensure we have events. 9. Click button to stop recording => Timeline plays nothing for 30 seconds and the shows events for the 1s of recording => Expected timeline to immediately jump forward 30s and show the events for the 1s of recording
<rdar://problem/21946519>
Created attachment 257300 [details] [PATCH] Proposed Fix
Comment on attachment 257300 [details] [PATCH] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=257300&action=review > Source/WebInspectorUI/UserInterface/Views/TimelineRecordingContentView.js:-520 > - Child records of the rendering frame are added to the other timelines, so this change would potentially net us an earlier current time, but the difference should be very small.
Comment on attachment 257300 [details] [PATCH] Proposed Fix View in context: https://bugs.webkit.org/attachment.cgi?id=257300&action=review > Source/WebInspectorUI/UserInterface/Views/TimelineRecordingContentView.js:-517 > - // The rendering frame timeline doesn't use a time axis. The axis type is irrelevant. A rendering frame record generally has an earlier start time than its first child, which we want to account for. We should remove this check.
Comment on attachment 257300 [details] [PATCH] Proposed Fix Clearing flags on attachment: 257300 Committed r187209: <http://trac.webkit.org/changeset/187209>
All reviewed patches have been landed. Closing bug.