[Libreoffice-ux-advise] [Bug 96274] Cannot Change Heading Style

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=96274

--- Comment #7 from thangalin at gmail.com ---
See Joel Spolsky's post http://www.joelonsoftware.com/items/2008/07/01.html .

See his comment
http://ux.stackexchange.com/questions/12756/dont-hide-or-disable-menu-items#comment15651_12761
:

"When I wrote the original blog post I was thinking of typical desktop
programming environments which did not, by default, provide any mechanism for
the user to learn why a menu item was disabled; they just left the user to
scratch their heads and caused a usability problem. If you are 100% confident
that your users will understand WHY something is disabled, or if you can
provide a tooltip explanation that will be easily found, disabling is fine."

What I mean by "never disable options" is echoed at
http://ux.stackexchange.com/a/12761/15694 :

"Explain why an item is disabled: Great advice that almost no one follows!
Google search 'greyed out menu' and you'll find heaps of people wondering why
their menu items are disabled, because the app doesn't tell them."

See http://ux.stackexchange.com/a/926/15694 :

"I generally have found that users don't read anything."

See http://ux.stackexchange.com/a/76155/15694 :

"Tooltips are a greta solution, but as you mentioned, many people are not aware
they are there. Thus this tiny indicator invites the user to look for help only
when they need it."

Without any usage statistics to back up the idea, it's anyone's guess as to
whether tooltips are actually helpful.

Therefore, my original premise stands. Don't disable anything. Leave everything
enabled and, when the user tries to use the feature, provide them practical
help on why the feature is unavailable and how to resolve the issue. Further,
this should not require the user going to external documentation (that is only
available via the Internet). Although it would be cool to have the internal
documentation link to a wiki or Q&A site that contains answers related to that
particular feature.

-- 
You are receiving this mail because:
You are on the CC list for the bug.