Repository navigation
fix(browser): trigger below-fold lazy assets in fixed mobile Main Platform public QA - #871
Merged
Merged
Conversation
…on and bounded timeout
kmjtechno
marked this pull request as ready for review
November 10, 2026 08:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Real authorized CodeBridge browser public QA executed on KMJ-elite at 2026-11-10T08:40 UTC (job
3b60b415-12e1-407e-9847-9eab2bc142e1). Nine fixed-origin screenshots were captured with verified hashes: desktop/,/products,/loginall HTTP 200, zero broken/pending/failed images, exceptions or overflow; tablet all PASS; mobile/productsand/loginPASS. Mobile/FAIL: HTTP 200, overflow 0, exceptions 0,brokenImages=17,pendingImages=17,failedImages=0, failurePENDING_IMAGES_TIMEOUT. This does not establish missing asset files: the browser harness originally changed existing lazy images to eager once before hydration, then waited 4+3 seconds without actually scrolling into view. Below-fold native lazy images and images inserted late by hydration can remain unrequested.This PR changes ONLY the fixed-origin, anonymous READ-ONLY CodeBridge QA harness. It runs a browser-internal bounded scroll from top toward at most 24,000px, 600px/60ms per step, max 41 steps, promoting visible and late-inserted native lazy images; then it restores scroll to top and prior scrollBehavior, preserves the original bounded 4s image settle and 3s pending-only second window, and still FAILS any remaining pending or hard-undecodable image. No source URLs, arbitrary navigation, credentials, process flags, remote debugging port, browser sandbox downgrade or cookie access; no production mutation.
Node VM adversarial tests simulate late-created offscreen images triggered by scrolling, bounded giant-document traversal, scroll restoration, and genuine permanently-pending images retaining
PENDING_IMAGES_TIMEOUT. Existing browser receipt/redaction tests and repo CI remain. Source merge is NOT proof the deployed CodeBridge agent has picked up this version or that the live mobile site is fixed; rerun the same 9-page read-only QA on an independently updated pinned agent before declaring PASS.