Status: 75% - We have a prototype to play with the UI
Previous RFC: RFC: Better chat @mentions
Problem Statement & Background
Please see the previous RFC.
The feedback to the solution I proposed in the original RFC was overwhelmingly positive. We now have a prototype of the chat input box's behavior under the new regime. It incorporates some of the suggestions made in response to the original post.
This is just that: a prototype. I'm not looking for bug reports on every minor issue; rather, I'd like to know whether it feels comfortable and non-awkward for you to compose chat messages in this way, and if it in any way breaks your flow and muscle memory when chatting.
For now this is intended to work in desktop Chrome and Firefox, it may or may not work completely in other browsers. Again, finding cross-browser bugs is not the purpose of this RFC. Of course the final version is supposed to work in all our supported browsers, including mobile ones.
Link to the prototype: http://chat.meta.stackexchange.com/prototypes/mention
- Undo/redo is spotty at best. Not that it's great in the current chat input box, but I'd like it to be better before release.
- The way that @mentions are displayed seems to suggest that you can interact with them (e.g. click on them to display the well-known user info popup), but that's not currently the case. See the next section for more.
- Can you work with this? Does it break the way that you're used to chatting? If so, how so?
- If you use assistive technology (e.g. screen readers), does it work for you? I know our chat is anything but the archetype of an accessible web application, but I certainly don't want to make matters worse.
- What should happen when you click a mention? Would you rather see the current behavior, which is closer to what you would expect from a normal text input box, or would you rather see the user info popup (or something else entirely)?
- Relatedly: At the moment, the underlying
@is exposed when you move the text cursor onto a mention. On the one hand, this keeps the behavior closest to that of a "real" text box (in particular, Ctrl-A Ctrl-C Ctrl-V works in obvious way). On the other hand, this may be too much of a power user-only thing to expose (I am not suggesting to break copy&paste in either case). What are your thoughts on this?
- Anything else?
If possible, when describing any behavior that felt irritating, also describe what you would've expected to happen instead.