Place Action Rich UI BELOW the assistant text - or have it be configurable #21482
Replies: 6 comments 11 replies
-
|
Here are two additional reasons for supporting the "Bottom" placement, focusing on logical flow and user behavior:
|
Beta Was this translation helpful? Give feedback.
-
|
@Fu-Jie we need more opinions here - if you know some people who might be interested in Rich UI and can share an opinion here that would be wanted and needed please 🙏 CC @ShirasawaSama in case you use rich ui? |
Beta Was this translation helpful? Give feedback.
-
|
CC @Ithanil are you interested in Rich UI for actions in general? If yes: what do you think about the current placement ON TOP of the message instead of at bottom (where the action button is)? |
Beta Was this translation helpful? Give feedback.
-
|
Tossing in my two cents. I 100% agree with @Classic298 and @Fu-Jie here—the current way the Action UI works is actually hurting the user experience, especially when we’re dealing with long-context responses. Here’s my breakdown of why we need to change this, or at the very least, make it a configurable setting. The Main Problem: The "Did It Work?" Factor If I’m on a laptop/phone or scrolling through a long thread, I literally can’t see the change. It feels like the button is broken. I have to manually scroll all the way back up just to see the visualization. In UX design, this breaks the "Visibility of System Status" principle. If I click something, I should see the reaction immediately, right where my eyes are focused. The Logical Flow: Context
Putting the result before the explanation (at the top) forces me to work backward. It’s like reading the punchline before the joke. The Compromise: Give us a Toggle My Proposal:
This way, power users who are dealing with massive outputs don't have to play the "scroll up and down" game, but we keep the flexibility for everyone else. This seems like a solid QoL (Quality of Life) update that would make the tool feel much more responsive. +1 from me on getting this implemented! |
Beta Was this translation helpful? Give feedback.
-
|
@Classic298 1. The "Artifact" Nature & Evolution 2. Community Precedent
If we change this to the top now, it goes against the established and intuitive flow that the community has already built. |
Beta Was this translation helpful? Give feedback.
-
|
Something else, which i think is acceptable, is now implemented: #21698 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Follow up discussion for: #21419
I am vouching for the placement of the Rich UI to be changed to BELOW the assistant message OR to be configurable if you'd want to place it above or below the assistant's message
Why?
Because
2.1) The Tool Rich UI is also placed exactly at it's invocation point, which is directly after the tool call.
2.2) So therefore, Action Rich UI should also be placed near the action button (which invoked the Rich ui)
@Fu-Jie additional reasons would be wanted here for vouching for this
CC @tjbck discussion created as demanded
Beta Was this translation helpful? Give feedback.
All reactions