Closed
Bug 570425
Opened 15 years ago
Closed 11 years ago
Line breaks are not honoured
Categories
(support.mozilla.org :: Forum, task, P4)
support.mozilla.org
Forum
Tracking
(Not tracked)
RESOLVED
FIXED
2014Q2
People
(Reporter: cilias, Assigned: rehandalal+mozilla)
References
Details
(Whiteboard: u=user c=questions p=2 s=2014.9)
1. Go to https://support-stage-new.mozilla.com/en-US/forums/test-b/722
2. Reply with 2 rows of text. e.g.
line 1
line 2
It gets posted as 1 line of text
Reporter | ||
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
This is part of Mediawiki markup. Single line breaks are ignore, double line breaks are not.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WONTFIX
Comment 3•14 years ago
|
||
Having to use html in a forum post is quite ugly. Is there a way to allow this in the forums/questions app? Possibly with the new parser?
Comment 4•14 years ago
|
||
I'm not really sure what the use case is though -- when do you need to put a new line of text right under the previous one, and why can't you then just use a new paragraph instead?
Comment 6•11 years ago
|
||
Re-opening via duplicate bug I filed.
Use case:
User is told to to us last 5 crash ids.
User pastes the crash ids on new lines and expects them to be separated by default, unfortunately,the user must hit enter twice for a new line or use <br> (line breaks) to make it work.
Comment 0 from Bug 935266:
We should make is default across all forums that when we hit enter for a new line, a line break is made and that we don't have to write a "<br>" every time we need to make a new line. This also confuses users as many users hit enter and expect a new line but instead this doesn't happen. This should be done for the support forum, the discussion forums, article discussions and with private messages as well.
SUMO Contributor forum thread about this: https://support.mozilla.org/en-US/forums/contributors/709735?last=55083
Status: RESOLVED → REOPENED
Component: Forum → General
OS: Mac OS X → All
Hardware: x86 → All
Resolution: WONTFIX → ---
Target Milestone: 2.1 → ---
Comment 7•11 years ago
|
||
Yeah, pasting crash IDs is a good point, Andrew. Do you have other cases for this? I'm asking since this would probably be a large change, and even investigating the scope would take time, so we should have a good reason to put in that time.
Priority: -- → P4
Comment 8•11 years ago
|
||
Another use case would be for new contributors trying not knowing about line breaks.
Another use case is when a user is responding and is on a new line when posting their reply but instead, it doesn't appear as the split up like how they wanted it to be. This make it jumbled for contributors to read and could possibly make the user aggravated.
Comment 9•11 years ago
|
||
Maybe an alternative would be to show a live preview of the post?
Comment 10•11 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #9)
> Maybe an alternative would be to show a live preview of the post?
That would work but users still don't know about <br>...
Comment 11•11 years ago
|
||
Adding to next sprint to get an estimation of scope.
Whiteboard: u=user c=questions p= s=2013.23
Comment 12•11 years ago
|
||
This *might* be a simple \n -> <br/> jinja2 filter (http://jbalogh.me/projects/jingo/#jingo.helpers.nl2br). Otherwise, we'll figure out something less simple.
Whiteboard: u=user c=questions p= s=2013.23 → u=user c=questions p=2 s=2013.backlog
![]() |
||
Comment 13•11 years ago
|
||
In all forums pressing enter for making new line is common. Anyway i think sumo forum will is not user friendly for normal users with this thing.
Comment 14•11 years ago
|
||
Brought up by ComputerWhiz in SUMO Community Discussion Forum: https://support.mozilla.org/en-US/forums/contributors/709960?last=57052#post-57052
Comment 15•11 years ago
|
||
Let's try the solution Ricky suggested. If that doesn't work, we can still decide if this is worth it.
Whiteboard: u=user c=questions p=2 s=2013.backlog → u=user c=questions p=2 s=2013.4
Updated•11 years ago
|
Target Milestone: --- → 2014Q1
Comment 16•11 years ago
|
||
Something that get on my nerves on the forms is the fact that you cannot simply go to the next line when typing something.
You either need to put the < br> HTML line break tag or double space the line.
Is there a specific reason for this?
Updated•11 years ago
|
Whiteboard: u=user c=questions p=2 s=2013.4 → u=user c=questions p=2 s=2013.backlog
Comment 18•11 years ago
|
||
We do have the icons to format as numbered or bulleted lists/paragraphs, but they are decidedly none intuitive in use as discussed in
"what am I doing wrong." https://support.mozilla.org/en-US/forums/contributors/710183
1. format list
2. then highlight
3. then use icon
Comment 19•11 years ago
|
||
John, can you file another bug for that? This one is about line breaks, which we should actually give another try.
Whiteboard: u=user c=questions p=2 s=2013.backlog → u=user c=questions p=2 s=2014.9
Comment 20•11 years ago
|
||
I will file a bug if you consider the icon based formatting system is worth changing. (If only to document better, or add an explanatory dropdown on mousover)
I added my last comment more as a reminder that if this particular change is considered costly we already have an existing system in place for precisely the use cases envisaged:
starting new lines
and creating lists.
Lists such as lists of five Crash IDs or sequential steps in an explanation.
The bulleted or numbered lists may be a better solution that the newline method being proposed here.
It makes me wonder do we really need the change discussed here.
Another alternative method of starting a new line is to use the <pre> </pre> markup tags, although as mentioned methods may not be user friendly or discoverable. Just preceding a line with a space immediately after the Return also has a similar effect but again is not easily discovered.
Comment 21•11 years ago
|
||
(In reply to John Hesling [:John99] from comment #20)
> I will file a bug if you consider the icon based formatting system is worth
> changing. (If only to document better, or add an explanatory dropdown on
> mousover)
John, it's not up to me to decide that. Madalina is the champion for the forums, for feature requests you should talk to her, but since this could also be seen as a bug, you could just go ahead and file it. In any case, I'm afraid putting a reminder into this bug won't help much.
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → rdalal
Comment 22•11 years ago
|
||
Pretty sure mythmon tried adding `white-space: pre;` and it fixes this issue.
Comment 23•11 years ago
|
||
Putting in the right component. There is no mention of questions (aka Support Forum) here, so we'll just do the discussion/contributor/community forums for now.
Component: General → Forum
Comment 24•11 years ago
|
||
Yes, please do this for the support forum as well. One major issue is that users don't know about our formating and are confused, so it would be particularly helpful for them.
Assignee | ||
Comment 25•11 years ago
|
||
Assignee | ||
Comment 26•11 years ago
|
||
Pushed to production a couple of hours ago by Ricky.
Status: REOPENED → RESOLVED
Closed: 15 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•