feat(conversational-ai): add multi-artifact demos and prompt-field up…#6332
feat(conversational-ai): add multi-artifact demos and prompt-field up…#6332TarunAdobe wants to merge 3 commits into
Conversation
…dates Introduce scroll-gallery and view-more Storybook demos for multi-file attachments, extend upload-artifact with media dismiss and badges, and align user-message styling with conversational AI audit designs. Co-authored-by: Cursor <cursoragent@cursor.com>
|
📚 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 |
Match Figma dismiss hit/visual layering on upload artifacts, prevent scroll-gallery clipping, add left-edge fade, and increase prompt-field and view-more control hit areas. Co-authored-by: Cursor <cursoragent@cursor.com>
Use spacing-75 instead of spacing-100 so the dismiss circle sits at Figma's 4px corner inset while keeping the 32px hit target. Co-authored-by: Cursor <cursoragent@cursor.com>
…dates
Introduce scroll-gallery and view-more Storybook demos for multi-file attachments, extend upload-artifact with media dismiss and badges, and align user-message styling with conversational AI audit designs.
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.