turbo:frame-missing: Re-use FetchResponse HTML

After re-considering a comment on [hotwired#445][], this commit
re-purposes the response HTML from the `FetchResponse` instance, instead
of issuing a follow-up HTTP request.

[hotwired#445]: hotwired#445 (comment)

Author: seanpdoyle

src/core/session.ts

@@ -309,9 +309,13 @@ export class Session
     this.notifyApplicationAfterFrameRender(fetchResponse, frame)
   }
 
-  frameMissing(frame: FrameElement, fetchResponse: FetchResponse): Promise<void> {
+  async frameMissing(frame: FrameElement, fetchResponse: FetchResponse): Promise<void> {
     console.warn(`Completing full-page visit as matching frame for #${frame.id} was missing from the response`)
-    return this.visit(fetchResponse.location)
+
+    const responseHTML = await fetchResponse.responseHTML
+    const { location, redirected, statusCode } = fetchResponse
+
+    return this.visit(location, { response: { redirected, statusCode, responseHTML } })
   }
 
   // Application events

src/tests/functional/frame_tests.ts

@@ -120,6 +120,7 @@ test("test following a link to a page without a matching frame dispatches a turb
   await noNextEventOnTarget(page, "missing", "turbo:frame-render")
   await noNextEventOnTarget(page, "missing", "turbo:frame-load")
   const { fetchResponse } = await nextEventOnTarget(page, "missing", "turbo:frame-missing")
+  await noNextEventNamed(page, "turbo:before-fetch-request")
   await nextEventNamed(page, "turbo:load")
 
   assert.ok(fetchResponse, "dispatchs turbo:frame-missing with event.detail.fetchResponse")