>I think they record whatever HTTP transactions you trigger, so they can be played back when triggered in the replay. That could be a useful history for circum

>I think they record whatever HTTP transactions you trigger, so they can be played back when triggered in the replay. That could be a useful history for circumventing forced usability reductions when a site 'upgrades' but doesn't change the request structure and/or doesn't deny access/EOL a previous API version but just hides the old interface after a makeover. For example: I would love to have a recording of sessions from the previous version of ESPN's html fantasy football interface with a record of request to see if I could roll my own so to speak. (ESPN ruined the usability of the site by rewriting it in some Javascript framework hoping to annoy users into app conversions last year.)