Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid setting a negative padding on the chat welcome view container #229996

Merged
merged 1 commit into from
Sep 27, 2024

Conversation

roblourens
Copy link
Member

The layout here is a bit weird to avoid shifting when followups appear. If the followups wrap, then the layout is messed up because negative padding is not allowed. I might try to simplify this for next month.
Fix microsoft/vscode-copilot#8749

The layout here is a bit weird to avoid shifting when followups appear. If the followups wrap, then the layout is messed up because negative padding is not allowed. I might try to simplify this for next month.
Fix microsoft/vscode-copilot#8749
@roblourens roblourens self-assigned this Sep 27, 2024
@roblourens roblourens merged commit 1b22d60 into release/1.94 Sep 27, 2024
7 checks passed
@roblourens roblourens deleted the roblou/impressed-damselfly branch September 27, 2024 21:08
roblourens added a commit that referenced this pull request Sep 27, 2024
…229996)

The layout here is a bit weird to avoid shifting when followups appear. If the followups wrap, then the layout is messed up because negative padding is not allowed. I might try to simplify this for next month.
Fix microsoft/vscode-copilot#8749
roblourens added a commit that referenced this pull request Sep 27, 2024
…229996) (#230029)

The layout here is a bit weird to avoid shifting when followups appear. If the followups wrap, then the layout is messed up because negative padding is not allowed. I might try to simplify this for next month.
Fix microsoft/vscode-copilot#8749
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.

2 participants