Fix Grok-style composer layout regression - #105
Open
faresmohamed260 wants to merge 2 commits into
Open
Conversation
|
Deployment failed for project studio with the following error: Learn More: https://vercel.com/faresmohamed260-6733s-projects?upgradeToPro=build-rate-limit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the production UI regression visible after PR #104. The app shell no longer reserves the removed right-side settings column, inline composer controls are forced to stay compact instead of inheriting full-width select styles, the toolbar stays on one row with horizontal overflow when needed, duplicate resolution text is suppressed, and the composer height is tightened. No Vercel deployment should be triggered manually until this is merged.