Page MenuHomePhabricator

Find a clear explanation for frameless “quiet” button application
Closed, DuplicatePublic

Description

What is the current application logic on when to use a “quiet” button versus a framed one?

image.png (102×974 px, 17 KB)

Event Timeline

Note that “quiet” in mediawiki.ui terms was referring to a default, framed button.

If you hope I have an explanation, then I have to disappoint you. I have no idea what is their purpose. I have always found the frameless/quiet buttons silly and I would like it if we never used them. I think in all cases either a normal button or a normal link is sufficient.

That page now says (after T329963):

Use Quiet Buttons for an easily recognizable action that does not detract focus from the content. Be conscious of the fact that Quiet Progressive Buttons can look similar to Links, so avoid using them next to each other.

Which is better than nothing, but still doesn't explain why you would use this kind of button instead of a normal button.

(My opinion on quiet buttons hasn't changed since my previous comment in 2019, I recently filed a task that explains it better: T336676: Deprecate the basic quiet button in Codex)