Await successful 204 response before request cleanup #46
Loading…
Reference in a new issue
No description provided.
Delete branch "oss-oo/frontdoor-v12-website-204-fix-599df7fbfc76"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem and resulting behavior
The native adapter returned immediately after successful 204 headers. That branch now awaits
response.text()exactly once before returning its existingnullresult and releasing its timer/controller. All other runtime code, including the original non-204response.json()and error flow, remains byte-for-byte unchanged. The existing 20-second timeout, AbortSignal and pagehide handling stay active through the awaited step.Verification
Scope and limitations
Local synthetic Chrome 156 controls and independent raw-CDP controls distinguish an awaited-codepath, timing or object-lifetime dimension. A 204 response has a null body; this is not a payload-drain claim or a proven unique Chrome 151/native cause. No browser-oracle exemption, native attempt, UI markup change, deployment or merge is included. Commons Website pairing fixtures require a separate reviewed successor after source acceptance; frozen inputs remain unchanged.
WIP: Await native response text before releasing request stateto WIP: Await successful 204 response before request cleanupWIP: Await successful 204 response before request cleanupto Await successful 204 response before request cleanup