Bug 129391

Summary: Web Replay: capture and replay ResourceLoader callbacks
Product: WebKit Reporter: Blaze Burg <bburg>
Component: Page LoadingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED LATER    
Severity: Major CC: ap, bburg, beidson, ddkilzer, joepeck, kling
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on: 129388, 129389, 130632, 130728, 130865    
Bug Blocks: 136290, 131318    
Attachments:
Description Flags
wip.1
none
the patch none

Blaze Burg
Reported 2014-02-26 14:09:19 PST
This is the main bug for replaying network traffic.
Attachments
wip.1 (48.16 KB, patch)
2014-03-24 08:48 PDT, Blaze Burg
no flags
the patch (52.03 KB, patch)
2014-03-30 22:59 PDT, Brian Burg
no flags
Blaze Burg
Comment 1 2014-03-24 08:48:01 PDT
Timothy Hatcher
Comment 2 2014-03-25 12:19:32 PDT
Comment on attachment 227649 [details] wip.1 View in context: https://bugs.webkit.org/attachment.cgi?id=227649&action=review > Source/WebCore/loader/ResourceLoader.h:47 > +namespace JSC { > +class InputCursor; > +} #ifdef ENABLE(WEB_REPLAY) too?
Brian Burg
Comment 3 2014-03-30 22:59:28 PDT
Created attachment 228152 [details] the patch
Brian Burg
Comment 4 2014-03-30 23:01:40 PDT
Uploaded a new patch rebased on top of fixes for 130728, 130865. Brady, I would appreciate it if you could look at this patch plus the one in 130865 to see how they work together.
Brady Eidson
Comment 5 2015-08-05 10:28:19 PDT
Comment on attachment 228152 [details] the patch How does this interact with the app cache?
Blaze Burg
Comment 6 2015-08-05 10:33:31 PDT
(In reply to comment #5) > Comment on attachment 228152 [details] > the patch > > How does this interact with the app cache? Good question! I don't think this patch considers app cache behavior. I'll have to look into it. This patch series is at least 6 months behind, so I am clearing r? flags for the time being.
Blaze Burg
Comment 7 2017-07-10 13:59:27 PDT
Closing web replay-related bugs until we resume working on the feature again.
Note You need to log in before you can comment on or make changes to this bug.