Closed
Bug 2026814
Opened 5 months ago
Closed 5 months ago
Add fade to chat overflow
Categories
(Core :: Machine Learning: Frontend, enhancement)
Core
Machine Learning: Frontend
Tracking
()
RESOLVED
FIXED
151 Branch
| Tracking | Status | |
|---|---|---|
| firefox151 | --- | fixed |
People
(Reporter: jlevinsohn, Assigned: giulia)
References
Details
(Whiteboard: [genai][chat])
Attachments
(5 files)
Chat content currently cuts off abruptly at the top and bottom when overflowing. A fade should be applied.
- A fade is applied at the top of the chat content when content is scrollable above
- A fade is applied at the bottom of the chat content when content overflows below
- Fade matches design spec for:
- color
- opacity
- gradient direction
- Fade appears only when content is overflowing (not when fully visible)
Figma Specs
Updated•5 months ago
|
| Reporter | ||
Comment 1•5 months ago
|
||
| Reporter | ||
Comment 2•5 months ago
|
||
| Reporter | ||
Comment 3•5 months ago
|
||
| Reporter | ||
Comment 4•5 months ago
|
||
There is a chance that with the gradient it is difficult to add a transparent linear gradient like this to the top and bottom of both full width and sidebar chat. If that's the case UX will explore a blur that visually appears similar.
| Assignee | ||
Updated•5 months ago
|
Assignee: nobody → gcardieri
| Assignee | ||
Comment 5•5 months ago
|
||
Updated•5 months ago
|
Attachment #9559590 -
Attachment description: WIP: Bug 2026814: Include fade on smart window chat wrapper → Bug 2026814: Include fade on smart window chat wrapper and adjust auto scroll
Pushed by gcardieri@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/58440b6ddd0d
https://hg.mozilla.org/integration/autoland/rev/62994adabba1
Include fade on smart window chat wrapper and adjust auto scroll r=ai-frontend-reviewers,echa
Status: NEW → RESOLVED
Closed: 5 months ago
status-firefox151:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 151 Branch
Updated•4 months ago
|
QA Whiteboard: [qa-triage-done-c152/b151]
You need to log in
before you can comment on or make changes to this bug.
Description
•