Skip to content

Fix responsive breakpoints for web component deployment#173

Merged
SukuWc merged 1 commit intomainfrom
SUKU-fix-responsive-breakpoints-webcomponent
Feb 10, 2026
Merged

Fix responsive breakpoints for web component deployment#173
SukuWc merged 1 commit intomainfrom
SUKU-fix-responsive-breakpoints-webcomponent

Conversation

@SukuWc
Copy link
Member

@SukuWc SukuWc commented Feb 10, 2026

Summary

  • Replace CSS @media queries with @container queries in ProfileCloudTreeItem.svelte and BrowserLayout.svelte
  • @media queries respond to the viewport width, which doesn't work when the app is embedded as a web component inside another application (e.g. Grid Editor) — the viewport is the full browser window, not the component's panel
  • @container queries respond to the nearest ancestor's container width, so breakpoints now trigger correctly based on the actual available space

Test plan

  • Verify the modified date hides in ProfileCloudTreeItem when the tree panel is narrower than 400px in the web component deployment
  • Verify the config grid in BrowserLayout switches from 1 → 2 → 3 columns at the correct breakpoints in the web component deployment
  • Verify the standalone app (non-web-component) still behaves correctly

🤖 Generated with Claude Code

Replace CSS @media queries with @container queries so breakpoints
respond to the component's container width instead of the viewport,
which doesn't work when embedded as a web component.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions
Copy link

Visit the preview URL for this PR (updated for commit a97cc60):

https://profile-cloud-dev--pr173-suku-fix-responsive-k3k3x84m.web.app

(expires Thu, 12 Mar 2026 14:30:51 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 2a004f867edf1347070dd9beedb18755187a6d4e

@SukuWc SukuWc merged commit 371e776 into main Feb 10, 2026
3 checks passed
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