feat: add new conversational-ai pattern#6087
Conversation
|
rubencarvalho
added
Status:WIP
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| .swc-MessageFeedback { | ||
| display: inline-flex; | ||
| align-items: center; | ||
| gap: 4px; |
There was a problem hiding this comment.
🚫 [stylelint] <order/properties-order> reported by reviewdog 🐶
Expected "gap" to come before "align-items"
|
|
||
| .swc-MessageFeedback-button:hover { | ||
| background: token("gray-100"); | ||
| color: token("gray-800"); |
There was a problem hiding this comment.
🚫 [stylelint] <order/properties-order> reported by reviewdog 🐶
Expected "color" to come before "background"
| .swc-MessageSuggestions-chip { | ||
| display: inline-flex; | ||
| align-items: center; | ||
| gap: 0; |
There was a problem hiding this comment.
🚫 [stylelint] <order/properties-order> reported by reviewdog 🐶
Expected "gap" to come before "align-items"
| .swc-MessageSuggestions-chip swc-icon { | ||
| --swc-icon-inline-size: 22px; | ||
| --swc-icon-block-size: 22px; | ||
| flex-shrink: 0; |
There was a problem hiding this comment.
🚫 [stylelint] <declaration-empty-line-before> reported by reviewdog 🐶
Expected empty line before declaration
| ::slotted(ul), | ||
| ::slotted(ol) { | ||
| margin: 0; | ||
| padding-inline-start: 20px; |
There was a problem hiding this comment.
🚫 [stylelint] <order/properties-order> reported by reviewdog 🐶
Expected "padding-inline-start" to come before "margin"
TarunAdobe
force-pushed
the
conversation-ai-pattern
branch
from
4e17a06 to
1627a02
Compare
…eb-components into conversation-ai-pattern
📚 Branch Preview Links🔍 First Generation Visual Regression Test ResultsWhen a visual regression test fails (or has previously failed while working on this branch), its results can be found in the following URLs:
Deployed to Azure Blob Storage: If the changes are expected, update the |
3 participants
Description
Motivation and context
Related issue(s)
Screenshots (if appropriate)
Author's checklist
Reviewer's checklist
patch,minor, ormajorfeaturesManual review test cases
Descriptive Test Statement
Descriptive Test Statement
Device review
Accessibility testing checklist
Required: Complete each applicable item and document your testing steps (replace the placeholders with your component-specific instructions).
Keyboard (required — document steps below) — What to test for: Focus order is logical; Tab reaches the component and all interactive descendants; Enter/Space activate where appropriate; arrow keys work for tabs, menus, sliders, etc.; no focus traps; Escape dismisses when applicable; focus indicator is visible.
Screen reader (required — document steps below) — What to test for: Role and name are announced correctly; state changes (e.g. expanded, selected) are announced; labels and relationships are clear; no unnecessary or duplicate announcements.