Page MenuHomePhabricator

When entering a section heading on the same line as text , it renders incorrectly.
Closed, InvalidPublic

Description

Author: mets501wiki

Description:
When entering a section heading on the same line as text, it does not render as
a heading, but rather as part of the paragraph, with "==" on each side of the
text. This is a problem for a variety of things including bots and applicatios
such as VandalProof, some of which rely on this feature for warning users about
vandalism.


Version: unspecified
Severity: normal

Details

Reference
bz6327

Event Timeline

bzimport raised the priority of this task from to High.Nov 21 2014, 9:17 PM
bzimport added a project: MediaWiki-Parser.
bzimport set Reference to bz6327.
bzimport added a subscriber: Unknown Object (MLST).

leon wrote:

Could you create an example test page, please? I don't really understand what
you're meaning.

leon wrote:

Ah, I got it. So what's the problem? It's looking ugly, and users should put
headings on a single line (my opinion).

robchur wrote:

Fix the bot so it adds a newline character at the end of section headings. This
is part of the markup.

mets501wiki wrote:

Yes, users should put headings on a their own line in most cases. However, for some uses, this is impossible to
do, so it would be nice if headings rendered even when not on their own line.

mets501wiki wrote:

How can it add a newline character?

leon wrote:

\n or \n\r are the regexps for newlines.

mets501wiki wrote:

Alright, I'll look into that. Thanks.

Sorry. "\n\r" is invalid. It should be "\r\n", the windows line breaking-chars.
However, the wiki only uses "\n".

mets501wiki wrote:

Alright. It's still a problem for VandalProof, though. Basically, if this bug takes 10 seconds to fix, then fix it,
otherwise (if it's more difficult) we'll find a workaround.

robchur wrote:

Fix. Your. Third party. Application.

mets501wiki wrote:

I sure hope that wasn't meant to be rude.
But yes, I'm sure there's a workaround.
It really wouldn't have been an issue in the first place, but it was working up until just before I started this bug
report, and then mysteriuosly stopped working.