Ttomar/upload artifact#6452
Conversation
…bnails Media artifacts no longer reserve space for an empty actions row, and thumbnail content is positioned to cover the full tile. Storybook demos now use stable picsum image previews instead of broken gradient placeholders. Co-authored-by: Cursor <cursoragent@cursor.com>
Support mixed file types with a bottom-left overlay on type="media" without introducing a new artifact type. Co-authored-by: Cursor <cursoragent@cursor.com>
…trips Match dismiss, radii, shadow, and badge spacing to design specs. Update docs and stories for card-only or media-only attachment strips, warn in prompt-field when types are mixed, and use media tiles with badges in the pattern overview demo. Co-authored-by: Cursor <cursoragent@cursor.com>
Add flanking chevron navigation and hidden-scrollbar trackpad scroll when multiple attachments overflow the composer. Refine media dismiss sizing for Figma alignment. 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 |
Mount mixed artifacts after the console.warn spy is installed, and read badge labels from the light DOM slot instead of shadow overlay textContent. Co-authored-by: Cursor <cursoragent@cursor.com>
Document required legal disclaimers with a dev warning when missing. Clarify that mixed uploads should normalize to media tiles with badges, not card and media layouts in the same strip. Co-authored-by: Cursor <cursoragent@cursor.com>
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.