I want to check if there is a use case for this control. The pop-up is un-selectable but I wonder if we'll ever need to hide info behind a button?
If they are selectable, I suggest that this becomes a regular menu instead.
• violetto | |
Feb 4 2015, 11:36 PM |
F57433: k9Fb0eK.png | |
Mar 7 2015, 1:13 AM |
F37356: Screenshot_2015-02-04_15.31.11.png | |
Feb 4 2015, 11:36 PM |
F37357: Screenshot_2015-02-04_15.31.17.png | |
Feb 4 2015, 11:36 PM |
I want to check if there is a use case for this control. The pop-up is un-selectable but I wonder if we'll ever need to hide info behind a button?
If they are selectable, I suggest that this becomes a regular menu instead.
That is a reasonable option if we want to support recurrent use (i.e., keeping the advanced tools more accessible for those that use them frequently once they open the menu once).
Current VE regular menu, where keyboard shortcuts are shown, may be enough for that purpose but I want like to check how (and how much) people are using these tools in "talk" context.
This is a pop-up that has unselectable items. Sounds like you guys are talking about menus?
They are about the same thing but they don't seem to be duplicates.
T88625 is about whether there is a use case for the widget
T87698 is accessibility related (covers both cases of T88630)
T88630 is the decision whether it should activate on click or hover
@violetto @matmarex, do you think we should update descriptions and merge all of them? It might be easier to have a discussion about all these at one place.
@TrevorParscal @matmarex @Prtksxna what is this control intended for?
Is it for use in areas like Flow text formatting toolbar or junk drawer / "more" menu type of control?
Had a similar question here about the frameless option.