Does colorScheme=light only work in embed mode? Also, when embedded, the peri...
Does colorScheme=light only work in embed mode? Also, when embedded, the periodic quotes aren't appearing on the home page.
1. colorScheme=light is gated on embed mode.
apps/web/components/embed-mode.tsx:23 — the theme override only fires when isEmbed is true:
if (isEmbed && (colorScheme === "light" || colorScheme === "dark")) {
setTheme(colorScheme);
}
So ?colorScheme=light alone does nothing — you need ?embed=true&colorScheme=light. If you want it to work standalone too, drop the isEmbed && guard (or split into a separate effect).
2. The floating quotes are hidden by responsive breakpoints, not by embed mode itself.
apps/web/components/floating-quotes.tsx:
- Normal terminal state (line 236):
hidden xl:block— quotes only appear at viewport ≥ 1280px - Expanded:
hidden 2xl:block— ≥ 1536px - Collapsed (line 169):
hidden md:block— ≥ 768px
The iframe you're embedding into is almost certainly narrower than the xl breakpoint, so the side-mounted quotes never render. They're also positioned absolutely at calc(50% + 400px) from center, which assumes a wide viewport.
Two fixes depending on what you want:
- If embedded views should never show floating quotes, skip rendering
<FloatingQuotes>when?embed=true(cleanest — they wouldn't fit anyway). - If you want them visible in the iframe, you'd need to either trigger the collapsed-state center layout in embed mode, or override the breakpoints / repositioning logic for embedded contexts.
Want me to wire up either fix?
Let's remove the color scheme gate on embed.
Done. Now ?colorScheme=light (or dark) sets the theme regardless of embed=true.
Your task
First, run git status, git diff, and git log --oneline -10 to understand the current state.
Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.
Single file change, no debug statements, no untracked files. Committing.
Committed as 214c9930. Branch is 1 ahead of origin/main — let me know if you want to push.
Your task
First, run git status, git diff, and git log --oneline -10 to understand the current state.
Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.
Routine dependency bumps across all packages plus lockfile — single logical change.
Committed as 0251e174. Branch is now 2 ahead of origin/main.
Your task
First, run git status, git diff, and git log --oneline -10 to understand the current state.
Then add and commit all modified files with a descriptive message. Break the changes into multiple commits if appropriate. If there are untracked files, ask if they should be added or added to the appropriate .gitignore file. The user may also want to take over at this point, so provide an abort option as well. Always check changes for unnecessary debugging statements or logging that might have been accidentally included. Prompt the user if you find any, and offer to remove each one by one. Do not use interactive git staging (git add -p) as it does not work.
Heads up before I commit: turbo got bumped to ^2.9.12 (caret-prefixed), but the project pins exact versions per CLAUDE.md. The previous entry was the exact 2.9.9. Want me to pin it as 2.9.12 before committing?
Lockfile now shows the exact pin. Committing.
Committed as 963a40f7 after pinning turbo to exact 2.9.12 and regenerating the lockfile. Branch is 3 ahead of origin/main.