Skip to content

Redesign the playground with shared glass controls - #2

Merged
Stianlars1 merged 1 commit into
mainfrom
codex/playground-material-redesign
Sep 12, 2026
Merged

Stianlars1 merged 1 commit into
mainfrom
codex/playground-material-redesign

Conversation

@Stianlars1

Copy link
Copy Markdown
Owner

The playground now follows the landing page's typography, neutral palette and material artwork. Soft forms, Hard light and Small world share their definitions with the landing, and the landing pill is both the fresh default and a reusable preset.

Shared glass buttons and native disclosure controls add subtle press and copy feedback. The editor preserves existing configuration URLs, manual save/load/delete, uploads, comparison tools, dragging and JSX/JSON export. Accessibility refinements cover keyboard focus, selected-state checks, persistent announcements, solid preference fallbacks and enlarged-text layouts.

Validation: 74 package tests and 27 demo tests, public/workspace type checks, lint and production builds passed. Browser checks covered the editing/export/persistence flows, all three scenes, light/dark and accessibility preferences, 320px reflow and 200% text sizing. The demo continues to consume react-glaze 0.1.2.

@vercel

vercel Bot commented Sep 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
react-glaze Ready Ready Preview Sep 12, 2026 10:13am UTC

Request Review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 12, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-12T10:19:22.422683Z 3e35c7f PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Stianlars1
Stianlars1 merged commit 91d04a5 into main Sep 12, 2026
4 checks passed

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3e35c7f2f3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

return `'use client';\n\n${clickable ? "import { useState } from 'react';\n" : ""}import { LiquidGlass } from 'react-glaze';\n\nexport function GlassExample() {\n${clickable ? " const [clicks, setClicks] = useState(0);\n" : ""} return (\n <>\n <LiquidGlass\n ${props.join("\n ")}\n style={{\n${styleCode}\n }}${clickable ? "\n onClick={() => setClicks(n => n + 1)}" : ""}\n >\n ${content}\n </LiquidGlass>${clickable ? '\n <p aria-live="polite">Clicks: {clicks}</p>' : ""}\n </>\n );\n}`;
const presentation =
state.example === "landing-pill"
? `\n <style>{${JSON.stringify('@font-face { font-family: "Glaze Inter"; src: url("https://react-glaze.app/fonts/inter-600.ttf") format("truetype"); font-weight: 600; font-display: swap; }\n' + pillResponsiveCss)}}</style>`

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Serve the exported pill font with CORS

When this generated JSX is pasted into an application hosted anywhere other than react-glaze.app, the @font-face request is cross-origin and browsers require the font response to grant CORS access. The repository's Next headers only cover the two historical HTML routes and do not add Access-Control-Allow-Origin for /fonts, so the request is rejected and the exported pill falls back to Helvetica instead of reproducing the advertised landing presentation. Export a consumer-owned font path or configure the font response for cross-origin use.

Useful? React with 👍 / 👎.

This branch was successfully deployed

1 active deployment
Preview — 3e35c7f2 Deployed Sep 11, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant