The discussion revolves around the user interface of the ‘Close’ button in the composer, where users are concerned that the button lacks clarity. jidanni argues that the button should display ‘Close…’ to indicate it triggers a dialog, as is common in other interfaces. Moin notes that the dialog does not always appear, making the ‘…’ potentially misleading. jidanni suggests the ‘…’ could appear only when text is entered, to avoid clutter. HamMan2118 mentions that admins can customize the text, but the focus is on a broader, universal fix. jidanni humorously illustrates how the button’s ambiguity could confuse users, emphasizing the need for clearer design.
Well, fine and good. But then “Close” should be “Close…” to let the user know about the coming dialog if s/he presses Close. It’s a standard feature, e.g., in your browser’s right click menus.
But the dialog will not necessarily appear. When you did not edit anything or your post/reply is not long enough, close will just close without an additional menu.
Today I had another encounter with this same Close button, in the same spot.
But maybe it was something I had for dinner, this time the “Close” button said to me, “I am the button to close the discussion, as it is getting off topic.”
It didn’t really say that to me, but with not even a mouseover, you can’t blame users for thinking it did.