Message menu, next step in place
Message menu, next step in place is a Context Menus block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Chat threads where a follow-up question (a reply, a report) belongs in the menu itself instead of a new surface
Anatomy
One card that never closes to ask the next question · a reaction track with a sliding single pick, then Reply, Copy text, Pin and Report · Reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send) · Report turns it into reasons, then a confirmation with Undo · the card grows and shrinks to fit the step · Back and Escape step back before the card closes, Tab stays inside while a step is open
In the Orvain Library
Get Message menu, next step in place for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Context Menus
What’s inside
06parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- One cardthat never closes to ask the next question
- A reaction trackwith a sliding single pick, then Reply, Copy text, Pin and Report
- Reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send)
- Report turns it into reasonsthen a confirmation with Undo
- The card grows and shrinks to fit the step
- Back and Escape step back before the card closes, Tab stays inside while a step is open
Responsive behaviour
640 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Context Menus earns its place
Reach for Context Menus
- A table or directory row needs per-record actions that would crowd the row if drawn inline
- A canvas or flow builder where a click should offer what can be added at that point
- A chat message needs reactions and replies without a permanent toolbar on every bubble
- A destructive action needs to sit apart from the ordinary ones, below a separator
Reach for something else
- The action is the main thing to do on the screen: put a button on the page, where a gesture nobody was told about cannot hide it
- You are choosing a value rather than firing an action: a dropdown reports the choice back to the control that opened it
- The panel would need its own search across hundreds of entries. That is a command menu, which is built to be typed at
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Message menu, next step in place” block to this page: one card that never closes to ask the next question, a reaction track with a sliding single pick, then Reply, Copy text, Pin and Report, Reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send), Report turns it into reasons, then a confirmation with Undo, the card grows and shrinks to fit the step, Back and Escape step back before the card closes, Tab stays inside while a step is open.
Questions about Message menu, next step in place.
What is the Message menu, next step in place block?
Message menu, next step in place is a Context Menus block from Orvain UI, built for React and Vue with a matching Figma frame. Best for chat threads where a follow-up question (a reply, a report) belongs in the menu itself instead of a new surface.
What is the Message menu, next step in place block made of?
6 parts: one card that never closes to ask the next question; a reaction track with a sliding single pick, then Reply, Copy text, Pin and Report; reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send); report turns it into reasons, then a confirmation with Undo; the card grows and shrinks to fit the step; and back and Escape step back before the card closes, Tab stays inside while a step is open. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Message menu, next step in place block responsive?
Yes. It is drawn at 640px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Message menu, next step in place block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Message menu, next step in place block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Message menu, next step in place block to this page.”
When should I not use a Context Menus block?
The action is the main thing to do on the screen: put a button on the page, where a gesture nobody was told about cannot hide it.
More Context Menus blocks
All Context MenusPremium components,
free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
Orvain MCPMessage menu, next step in place
Message menu, next step in place is a Context Menus block from Orvain UI, built for React and Vue with a matching Figma frame.
Best for
Chat threads where a follow-up question (a reply, a report) belongs in the menu itself instead of a new surface
Anatomy
One card that never closes to ask the next question · a reaction track with a sliding single pick, then Reply, Copy text, Pin and Report · Reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send) · Report turns it into reasons, then a confirmation with Undo · the card grows and shrinks to fit the step · Back and Escape step back before the card closes, Tab stays inside while a step is open
In the Orvain Library
Get Message menu, next step in place for your product
The block’s code in React and Vue, its frame in the Figma file, and the Orvain MCP so your AI tools build with it. Part of every Library plan, alongside every other block.
- React
- Vue
- Figma frame
- Orvain MCP
About this block
Part of Context Menus
What’s inside
06parts
The pieces it is built from. Keep them all, or drop the ones your product doesn’t need.
- One cardthat never closes to ask the next question
- A reaction trackwith a sliding single pick, then Reply, Copy text, Pin and Report
- Reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send)
- Report turns it into reasonsthen a confirmation with Undo
- The card grows and shrinks to fit the step
- Back and Escape step back before the card closes, Tab stays inside while a step is open
Responsive behaviour
640 px
Drawn at this width and never stretched past it. Below it, controls, text and spacing step down from the box the block sits in, not the window.
When to use it
Where Context Menus earns its place
Reach for Context Menus
- A table or directory row needs per-record actions that would crowd the row if drawn inline
- A canvas or flow builder where a click should offer what can be added at that point
- A chat message needs reactions and replies without a permanent toolbar on every bubble
- A destructive action needs to sit apart from the ordinary ones, below a separator
Reach for something else
- The action is the main thing to do on the screen: put a button on the page, where a gesture nobody was told about cannot hide it
- You are choosing a value rather than firing an action: a dropdown reports the choice back to the control that opened it
- The panel would need its own search across hundreds of entries. That is a command menu, which is built to be typed at
Accessibility
06to keep
What the block ships with. Hold on to these as you make it yours.
- Named controlsEvery icon-only button keeps a text label, so a screen reader can say what it does.
- Keyboard firstEvery control is reachable with Tab, and its focus ring stays visible.
- More than colourA state never rides on colour alone; a mark or a word goes with it.
- Contrast holdsRetheme freely, but keep text at or above the contrast it ships with.
- Calm motionFor visitors who ask for reduced motion, things simply appear.
- Room to hitTargets stay at least 24px, with space between neighbours.
Notes for AI
1 line
Is all your assistant needs. With the Orvain MCP connected, it builds the block from your own tokens and components.
Add the Orvain “Message menu, next step in place” block to this page: one card that never closes to ask the next question, a reaction track with a sliding single pick, then Reply, Copy text, Pin and Report, Reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send), Report turns it into reasons, then a confirmation with Undo, the card grows and shrinks to fit the step, Back and Escape step back before the card closes, Tab stays inside while a step is open.
Questions about Message menu, next step in place.
What is the Message menu, next step in place block?
Message menu, next step in place is a Context Menus block from Orvain UI, built for React and Vue with a matching Figma frame. Best for chat threads where a follow-up question (a reply, a report) belongs in the menu itself instead of a new surface.
What is the Message menu, next step in place block made of?
6 parts: one card that never closes to ask the next question; a reaction track with a sliding single pick, then Reply, Copy text, Pin and Report; reply turns the card into a composer with the message quoted (Cmd or Ctrl and Enter send); report turns it into reasons, then a confirmation with Undo; the card grows and shrinks to fit the step; and back and Escape step back before the card closes, Tab stays inside while a step is open. Keep them all, or drop the ones your product does not need; the rest of the block holds together without them.
Is the Message menu, next step in place block responsive?
Yes. It is drawn at 640px and never stretched past that. Below it, its controls, text and spacing step down with the container the block sits in rather than the browser window, so it holds up in a sidebar, a tablet layout and a 390px phone without clipping or sideways scrolling.
Is the Message menu, next step in place block accessible?
It ships with text labels on every icon-only button, full keyboard reach with a visible focus ring, states that never rely on colour alone, text contrast that holds when you retheme it, no animation for visitors who ask for reduced motion, and click targets of at least 24px.
How do I add the Message menu, next step in place block to my project?
It is part of every Orvain Library plan: the React and Vue code, its frame in the Orvain Figma file, and the Orvain MCP server. With the MCP connected, an AI assistant such as Claude Code, Cursor or v0 can build it from one line: “Add the Orvain Message menu, next step in place block to this page.”
When should I not use a Context Menus block?
The action is the main thing to do on the screen: put a button on the page, where a gesture nobody was told about cannot hide it.
More Context Menus blocks
All Context MenusPremium components, free in your inbox.
Join the Orvain Dispatch and get production-ready components, free to keep: React and Vue code plus the Figma frame, yours to ship.
