Add secure, reopenable HTML artifact previews - #94
Conversation
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (32)
Comment |
What changed
srcdocCSP that blocks outbound network access.Why
Generated HTML should behave like a reopenable artifact without letting model-authored scripts inherit application privileges or silently contact external hosts. The previous streaming and settled states also used different controls, which caused expansion and multi-artifact state bugs.
How it was verified
pnpm test— 291 passed, 7 skippedpnpm buildgit diff --check codex/provider-configuration..HEADScreenshots (UI changes)
The artifact flow was manually exercised in the local Electron app during PR #74. This split retains only the HTML artifact implementation and its security boundary.
Checklist
pnpm typecheckandpnpm testpass locallydist-server/edits or dependency/lockfile churnStack
This fork-based stack targets upstream
main; this PR will be rebased after #93 lands so its visible diff collapses to this slice.