Bug 356140 - Desktop notifications regard new line in pop-up but not in history
Summary: Desktop notifications regard new line in pop-up but not in history
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Notifications (show other bugs)
Version: 5.4.0
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: 1.0
Assignee: Martin Klapetek
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-12-01 04:36 UTC by Johnny Wezel
Modified: 2018-10-27 04:21 UTC (History)
2 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 Johnny Wezel 2015-12-01 04:36:19 UTC
A notification containing new line characters is displayed correctly in the pop-up. In the history, however, new line characters are displayed as a space character.

Reproducible: Always

Steps to Reproduce:
1. notify-send "title" "aaa
bbb"

Actual Results:  
Displays

aaa
bbb

in the pop-up, but

aaa bbb

in the history

Expected Results:  
History texts should be displayed regarding new line character. Each input line should appear on its own line in the history display field
Comment 1 Martin Klapetek 2015-12-02 20:11:12 UTC
Thanks for the report

This is done by design as the applet that you open from the panel has very limited space.

Can you state which usecases in particular it breaks for you?
Comment 2 Johnny Wezel 2015-12-02 21:59:13 UTC
Well the most important use case is common sense.

Then, the open panel scrolls and has thus a whole lot of space. 
Then, when there are a lot of lines in an entry the text becomes completely incomprehensible and the whole thing becomes unusable.
Comment 3 Martin Klapetek 2015-12-02 23:51:46 UTC
> Well the most important use case is common sense.

Yes. In our case, the common sense says trim unnecessary whitespace
when your screen real estate is limited.

> Then, when there are a lot of lines in an entry the text becomes completely incomprehensible and the whole thing becomes unusable.

I'm wondering - what sends such a long notifications? Can you give me
any particular example?
Comment 4 Andrew Crouthamel 2018-09-25 21:40:18 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-27 04:21:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!