You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can we improve playback experience when the target URL has a mime-type that normally could be displayed inline in the browser, but was served with a content-disposition: attachment header? (Example: 3YC2-DPRH).
You could also argue that all of this would be more cleanly handled from within the replay software itself, without recourse to any metadata stored externally.
The text was updated successfully, but these errors were encountered:
Can we improve playback experience when the target URL has a mime-type that normally could be displayed inline in the browser, but was served with a
content-disposition: attachment
header? (Example: 3YC2-DPRH).Optimally, we would serve an interstitial instead, similar to those we use for things that can't be rendered inline.
If we wanted to do this on our end, we would look for that header during the capture process while inspecting the first contentful response and store it alongside content-type, and then adapt our existing interstitial setup.
You could also argue that all of this would be more cleanly handled from within the replay software itself, without recourse to any metadata stored externally.
The text was updated successfully, but these errors were encountered: