Skip to content

Feat: horizontal chat (#3578) - #3576

Open
dennisrijsdijk wants to merge 3 commits into
crowbartools:v5from
dennisrijsdijk:feat/horizontal-chat
Open

Feat: horizontal chat (#3578)#3576
dennisrijsdijk wants to merge 3 commits into
crowbartools:v5from
dennisrijsdijk:feat/horizontal-chat

Conversation

@dennisrijsdijk

@dennisrijsdijk dennisrijsdijk commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

Description of the Change

This PR adds a horizontal chat mode to the built-in chat widget, letting chat messages render right-to-left (default, newest message starts on the right of the widget and pushes older messages to the left) or left-to-right (reversed, newest message starts on the left of the widget and pushes older messages to the right)

Applicable Issues

#3578

Testing

Ensured vertical mode still behaves as it did before
Ensured messages appear horizontally and don't break into multiple lines
Ensured when using horizontal mode, the horizontal alignment option is hidden and internally forced to left for a more consistent experience with shared chat info and announcements

Screenshots

image image

@dennisrijsdijk dennisrijsdijk changed the title Feat: horizontal chat Feat: horizontal chat (#3578) Sep 11, 2026
messageStyle: "compact" | "modern";
chatOrder: "normal" | "reversed";
/** The type of the chat (vertical or horizontal, undefined = vertical) */
chatType: "vertical" | "horizontal" | undefined;

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Could we name this field orientation instead of chatType? I think orientation would be more precise and not need a clarifying comment.

},
{
name: "chatType",
title: "Chat Type",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Same as with the field. I think this would be clearer as "Orientation" rather than "Chat Type"

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