Page MenuHomePhabricator

Paragraphs not respected within <blockquote>
Closed, ResolvedPublic

Description

Author: JoostMeerten

Description:
Within <blockquote>, paragraph breaks are not respected and all text is output
as a single paragraph instead. This makes it practically mandatory to break them
up and use the : syntax for indenting, losing the semantic info that a single
quote is presented.

For example,

<blockquote>
Lorem ipsum dolor sit amet.

Lorem ipsum dolor sit amet.
</blockquote>

Outputs:

<blockquote>
<p>Lorem ipsum dolor sit amet. Lorem ipsum dolor sit amet.</p>
</blockquote>

Rather than:

<blockquote>
<p>Lorem ipsum dolor sit amet.</p>
<p>Lorem ipsum dolor sit amet.</p>
</blockquote>

Paragraph tags can be added manually, but this should not be necessary.


Version: 1.4.x
Severity: normal
See Also: T53086

Details

Reference
bz1857

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 21 2014, 8:19 PM
bzimport added a project: MediaWiki-Parser.
bzimport set Reference to bz1857.

<blockquote> element does not format text like the <pre> element
so you have to use <br /> to break lines.

The <p> elements are added by tidy and the actuall output works
as expected (aka removing useless carriage return).

JoostMeerten wrote:

That's fine for HTML, but wiki syntax actually relies on these "useless carriage
returns" to produce paragraphs. Unlike HTML, they are not redundant. I
understand how this would be classified "not a bug", but it violates the
principle of least astonishment. Entering:

This is not one paragraph.

It's two.

Produces:

<p>This is not one paragraph.</p>
<p>It's two.</p>

When the text is *not* within <blockquote>. What is expected is not the removal
of whitespace but the automatic conversion of lines separated by two newlines to
paragraphs. It seems odd that we would require people to know about the oddities
of HTML/SGML in such cases when we go to pains to conceal them at other points.

michael wrote:

How does this relate to Bug 6200? Did that patch fix this bug?

ayg wrote:

Dunno why Hashar marked this FIXED.

*** This bug has been marked as a duplicate of 6200 ***