Bug 390071 - better visualize availability of HTML email version
Summary: better visualize availability of HTML email version
Status: REPORTED
Alias: None
Product: kmail2
Classification: Applications
Component: message list (show other bugs)
Version: Git (master)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-08 12:46 UTC by Milian Wolff
Modified: 2020-04-11 09:42 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Milian Wolff 2018-02-08 12:46:11 UTC
Volker just showed me how to switch between a plain-text email and its HTML version: Click on the vertical (!) "Plain Message" text in the grey bar next to the text. That is super non-obvious...

I'd prefer if mixed-mime messages with both HTML and Plain message also get a clear indication about the availability of an HTML version in the Fancy header, similar to pure HTML mails. Additionally, the "Plain Message" vertical text should at least get a Pointer cursor and some hover effect to make it clear that you can interact with this like with a button.

Finally please also add an action to switch between Plain and HTML versions to the context menu on the message view.
Comment 1 Omar Plummer 2018-02-08 18:26:00 UTC
Seconded.
Comment 2 Laurent Montel 2018-02-09 07:12:20 UTC
Git commit b96807b2cc7ee94e2bee2c68a0e492170ffba030 by Laurent Montel.
Committed on 09/02/2018 at 07:11.
Pushed by mlaurent into branch 'master'.

Add different cursor when we point on htmlstatusbar

M  +1    -0    messageviewer/src/widgets/htmlstatusbar.cpp

https://commits.kde.org/messagelib/b96807b2cc7ee94e2bee2c68a0e492170ffba030
Comment 3 Laurent Montel 2018-02-09 07:14:22 UTC
(In reply to Milian Wolff from comment #0)
> Volker just showed me how to switch between a plain-text email and its HTML
> version: Click on the vertical (!) "Plain Message" text in the grey bar next
> to the text. That is super non-obvious...
> 
> I'd prefer if mixed-mime messages with both HTML and Plain message also get
> a clear indication about the availability of an HTML version in the Fancy
> header, similar to pure HTML mails.


 Additionally, the "Plain Message"
> vertical text should at least get a Pointer cursor and some hover effect to
> make it clear that you can interact with this like with a button.

Done

> 
> Finally please also add an action to switch between Plain and HTML versions
> to the context menu on the message view.

Nope I will not add more menu entry as I reduce it.

We have statushtmlbar for it.

Regards
Comment 4 Milian Wolff 2018-02-14 10:05:28 UTC
then maybe I need to use statushtmlbar, can you give more explanation on how to use it? Maybe it should be the default?
Comment 5 Laurent Montel 2018-02-14 10:44:31 UTC
(In reply to Milian Wolff from comment #4)
> then maybe I need to use statushtmlbar, can you give more explanation on how
> to use it? Maybe it should be the default?

it's by default from long time :)

And you just need to click on it :)
Comment 6 Milian Wolff 2018-02-15 09:02:10 UTC
Well, I don't have it apparently - and I have no clue how to change it. So what is statushtmlbar and how do I get it?
Comment 7 Laurent Montel 2018-02-15 09:06:19 UTC
Configure->apperance->general-> Show HTML Side bar
Comment 8 Milian Wolff 2018-02-15 09:25:30 UTC
ah, so that _is_ the vertical tab :-/

I was hoping for a clearly clickable text in the header where it also says "From:" and so forth. If it would say "HTML Version Available" there in link font color, it would be much clearer that you can actually interact with this, compared to the vertical tab.

Additionally, we should consider changing the text of the vertical tab: "Plain Message" does not indicate that I can change to a HTML version by clicking on it. So maybe we rephrase that to "Plain Message (click to change to HTML)". Similarly do the opposite for "HTML Message (click to change to Plain)".
Comment 9 null 2020-04-11 09:42:10 UTC
Sounds similar to Bug 412190, which was closed in favour of Bug 399245. Should we close this one too as a duplicate?