[kmail2] [Bug 399245] New: Restore UI functionality related to "Show HTML side bar"

[pqz]

https://bugs.kde.org/show_bug.cgi?id=399245

Bug ID: 399245
Summary: Restore UI functionality related to "Show HTML side
bar"
Product: kmail2
Version: Git (master)
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: UI
Assignee: kdepim-***@kde.org
Reporter: ***@qbitdepot.com
Target Milestone: ---

After updating Kmail to 5.8.0, it is no longer possible to hide the "HTML side
bar". In KMail 5.7.3 there is a checkbox (Show HTML side bar) in the Setting
dialog, in Appearance -> General.

This was reported as bug 393595 and bug 393421 (closed), but as requested by
***@krop.fr, reopening again as a "feature request".

[Störm Poorun]

https://bugs.kde.org/show_bug.cgi?id=399245

Störm Poorun <***@olan.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@olan.org

--- Comment #1 from Störm Poorun <***@olan.org> ---

Great. Though it's not clear why the previous bug couldn't be converted to a
'feature request' and re-opened?

That would be preferable given the subscribers and comments are already
associated with that Bug.

https://bugs.kde.org/show_bug.cgi?id=393421


When most Users use their email app they do not expect to

a) view on each email a hideous line which should have stayed in the 1990s,
which a user may not need and can't turn off

b) view a warning box on each email, which can't be turned off (except on each
email individually).
"Note: This HTML message may contain external references to images etc. For
security/privacy reasons external references are not loaded. If you trust the
sender of this message then you can load the external references for this
message by clicking here."

This is an affront to Users a terrible impact on workflow, those dealing with
casual email will find it intrusive enough. Those dealing with thousands of
messages a day do not need that message in a red box taking priority on each
email they read.

There needs to be settings:
a) in the menu (like there was previously) to hide the warnings
b) in the menu to display html
c) in a pop up if a user closes the message, enable them to hide the warnings
in future
d) in a pop up if a users chooses to view .html mail, to permit them to
autodisplay .html mail in future
e) make the toggle bar less intrusive and less abrubt

[Nate Graham]

https://bugs.kde.org/show_bug.cgi?id=399245

Nate Graham <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@kde.org
Keywords| |usability

[Dmitry Ivanov]

https://bugs.kde.org/show_bug.cgi?id=399245

Dmitry Ivanov <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Erik Quaeghebeur]

https://bugs.kde.org/show_bug.cgi?id=399245

Erik Quaeghebeur <***@equaeghe.nospammail.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@equaeghe.nospammail.net

--- Comment #2 from Erik Quaeghebeur <***@equaeghe.nospammail.net> ---
(In reply to pqz from comment #0)

Post by pqz
After updating Kmail to 5.8.0, it is no longer possible to hide the "HTML
side bar". In KMail 5.7.3 there is a checkbox (Show HTML side bar) in the
Setting dialog, in Appearance -> General.
This was reported as bug 393595 and bug 393421 (closed), but as requested by

There is some misunderstanding here. First, *I* suggested you open a new bug.
Second, I suggested that you open a feature request bug for your UI
*modification* suggestions, not for the reinstatement of the existing
configuration option, which is bug 393421. Currently, this is just a duplicate
of that bug. Please read the comments more carefully to avoid duplication of
effort.

[pqz]

https://bugs.kde.org/show_bug.cgi?id=399245

--- Comment #3 from pqz <***@qbitdepot.com> ---
Sorry for the name (author) related misunderstanding (for some reason I though
you are one of the git committers, but I admit I did not check git logs).

The current ticket does not reinstate bug 393421, is just describing the
situation created by the change in the standard (default) settings dialog. The
ticket does not suggest to restore the previous code, is just asking for a way
to achieve the same functionality and that may be through a plugin or direct in
standard settings dialog.

What is the "duplicated effort" here? We mean somebody will "work" again then
"triage" and close this ticket also ? Can we stop focusing on how is this issue
reported and instead focus on the reported problem?

[Jonathan Marten]

https://bugs.kde.org/show_bug.cgi?id=399245

Jonathan Marten <***@keelhaul.me.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@keelhaul.me.uk

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=399245

--- Comment #4 from Christophe Giboudeaux <***@krop.fr> ---
Making noise just wastes everyone's time.

Erik's suggestion was correct. The question is not whether this option should
come back or not, the maintainer already said it won't.

Suggesting UI changes *is* the way to go.

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=399245

Christophe Giboudeaux <***@krop.fr> changed:

What |Removed |Added
----------------------------------------------------------------------------
Keywords|usability |

[pqz]

https://bugs.kde.org/show_bug.cgi?id=399245

--- Comment #5 from pqz <***@qbitdepot.com> ---
(In reply to Christophe Giboudeaux from comment #4)

Post by Christophe Giboudeaux
Making noise just wastes everyone's time.
Erik's suggestion was correct. The question is not whether this option
should come back or not, the maintainer already said it won't.
Suggesting UI changes *is* the way to go.

You should learn to respect other people opinions. "Making noise" is not an
appropriate language and/or attitude.

[Christophe Giboudeaux]

https://bugs.kde.org/show_bug.cgi?id=399245

--- Comment #6 from Christophe Giboudeaux <***@krop.fr> ---
I can close as duplicate of the other bug report where most comments can be
reduced to "+1" if you prefer.

[imraro]

https://bugs.kde.org/show_bug.cgi?id=399245

imraro <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[Alexander Wilms]

https://bugs.kde.org/show_bug.cgi?id=399245

Alexander Wilms <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

[avlas]

https://bugs.kde.org/show_bug.cgi?id=399245

avlas <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #7 from avlas <***@gmail.com> ---
What about start improving the UI by fixing this
https://bugs.kde.org/show_bug.cgi?id=393421#c47

In brief, the colors of the html bar have no effect in Kontact

[shevegen]

https://bugs.kde.org/show_bug.cgi?id=399245

shevegen <***@gmail.com> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@gmail.com

--- Comment #8 from shevegen <***@gmail.com> ---
(In reply to Christophe Giboudeaux from comment #6)

Post by Christophe Giboudeaux
I can close as duplicate of the other bug report where most comments can be
reduced to "+1" if you prefer.

While you could reason that way, the problem is that the other thread has lots
more comments than the one here, so this is not ideal for discussions.

I think it may have been better to mark the original one as a feature request
and keep it open. Nobody would force xyz or you to work on it - it would just
be one feature request of many more (or, in the event that it removed existing
functionality, a regression, in which case the question is whether developers
should have a higher right to modify code that affects the users, and I think
the users should have a higher right if it comes to any functionality that has
been working at some point. Losing functionality is always bad.).