Document page load wait strategy and live view URL handling - #567
Closed
robertjamesprior wants to merge 1 commit into
Closed
robertjamesprior wants to merge 1 commit into
robertjamesprior wants to merge 1 commit into
Conversation
Performance only covered browser creation latency. Add a page load section with the measured comparison: domcontentloaded plus a selector against load, and the fact that networkidle may never resolve on a long-dwell single-page app. Live view documented readOnly as making the view non-interactive, with nothing about the URL granting control of the browser or readOnly not being enforced server-side. Add a section on handling the URL as a credential, and qualify the readOnly bullet to point at it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
robertjamesprior
deleted the
hypeship/page-latency-and-live-view-security
branch
September 14, 2026 11:50
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
1 participant
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.
Summary
Two gaps where we have guidance that isn't written down publicly.
browsers/performance— page load latencyThe page covered browser creation latency in detail and said nothing about page latency, which is the part a browser agent actually spends its time on.
Adds a section with the measured comparison from a production workload:
domcontentloaded+ selectorloadnetworkidledid not resolve within an additional 10s budget on either page type, and can never resolve on a long-dwell single-page app.The recommendation is deliberately not "always use
domcontentloaded" — it'sdomcontentloadedplus the exact actionable selector, because a content-heavy page can reach an app-ready state well afterdomContentLoadedfires. That caveat is in aWarningso it doesn't get lost.browsers/live-view— treat the URL as a credentialThe page documented
readOnlyas "the view will be non-interactive" and had no security guidance at all. A developer reading it reasonably concludesreadOnly=truemakes the URL safe to hand out.Adds a section covering that the URL grants control of the browser, that
readOnlyis a display option rather than a security boundary, and that deleting the browser is the revocation path. The existingreadOnlybullet now points at it.Written as guidance about what not to rely on — it does not describe how the limitation is reached. Deliberately framed so embedding the live view in your own app reads as the intended use, because it is; the point is that your application decides who reaches the URL.
Verification
playwright.executeidiom already used inbrowsers/playwright-executionexample.comas the example host, consistent with the existing Playwright pagesURL lifetimesection rather than restating it; the new section links to it/browsers/termination,#url-lifetime,#treat-the-url-as-a-credential) resolve to real pages and headingsmintlify dev. Worth a preview check on the two new in-page anchors before merge.Context
browsers/live-viewwas previously tracked as KERNEL-2219, which was closed as not-planned when this content was covered in a customer-facing guide instead. That guide only reaches people we send it to, so the public gap stayed open — this closes it.🤖 Generated with Claude Code