Skip to content

feat(web): v8 sites always get the new blocks editor; no async rendering on v8 - #7827

Open
tlgimenes wants to merge 3 commits into
split/27-protocol-fieldsfrom
split/28-v8-blocks-editor
Open

tlgimenes wants to merge 3 commits into
split/27-protocol-fieldsfrom
split/28-v8-blocks-editor

Conversation

@tlgimenes

@tlgimenes tlgimenes commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Part of the v8 Studio stack, split from #7728, #7770 and #7766 (closed). Base: #7796. The top of the stack, #7843, has the same code as those three PRs combined.

v8 sites always get the new blocks editor, and the async-rendering controls show only on sites known to be v7.

What to look at: undefined while detecting (no editor flash); async UI only on known-v7 sites

Stack (web track, plan PR 28 of 20–41): previous #7826 · next #7828

🤖 Generated with Claude Code

https://claude.ai/code/session_01WNwbSEePYNcY5YCgqZURig

…ing on v8

v8 sites always get the new blocks editor, and the async-rendering
controls show only on sites known to be v7.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01WNwbSEePYNcY5YCgqZURig

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

claude PR authored by a coding agent

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant