https://bugs.kde.org/show_bug.cgi?id=440693
--- Comment #2 from Dawid Wróbel <m...@dawidwrobel.com> --- Created attachment 141242 --> https://bugs.kde.org/attachment.cgi?id=141242&action=edit macOS example OK, so in order to see the split contents, one has to: 1) Enable the "Ledger lens", which is not enabled by default 2) However over the "split transaction" text and wait a bit until the list is shown Splitting transactions is a core functionality of double-ledger bookkeeping software, so a modern UX guidelines in this case would dictate that the split contents should be visible to users without extra non-intuitive hops. Right now not only a user has to enable a non-default feature that is named ambiguously, then also have to "bump" into that information by accident, because the nature of a tooltip is so that it's not immediately known to a user that an information would be presented such way until they first see it. Most users expect them to explain the feature/checkbox/radio button etc. under a cursor, not to present extra information. So, in other words, this is not something majority of users will figure out by their own and will lead to frustration and support requests. Last, not least, tooltips simply don't exist on mobile/touch operated platforms, so that information would be unavailable there. All of the above is why the modern UX/UI dictates that tooltips should generally speaking *not* be used for such purposes. And because of the mobile/touch platforms, the modern UI should ideally getaway without using them at all, by making the UI self-explanatory and having the whatever tooltip information would be directly visible on the screen as a subscript of an option (see macOS screenshot example attached). -- You are receiving this mail because: You are the assignee for the bug.
