Last modified: 2012-02-02 19:52:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T35918, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 33918 - List syntax should allow multiple new lines between list items without starting a new list
List syntax should allow multiple new lines between list items without starti...
Status: RESOLVED DUPLICATE of bug 9996
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-24 00:50 UTC by vlakoff
Modified: 2012-02-02 19:52 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description vlakoff 2012-01-24 00:50:03 UTC
Currently, if lines beginning with a « * » (for <ul>'s) are separated by an empty line, they are rendered as separate <ul>'s.

i.e. "* foo\n\n* bar" is rendered as "<ul><li>foo</li></ul> <ul><li>bar</li></ul>"

We encounter a lot of cases like that, because contributors may think the wikisource is more readable so, and they don't notice the semantic failure.

In the case of "*", we can be pretty sure the contributor intended to make a single list. So I suggest we could be more tolerant and discard empty lines.

The case of "#" (<ol>) might require some examination of its uses on wikis before, but I think it may be readily feasible too.
Comment 1 Bawolff (Brian Wolff) 2012-01-24 00:51:56 UTC
Its also a common error that new users make on Wikinews.


Of course, touching the parser is scary!
Comment 2 Mark A. Hershberger 2012-01-30 16:49:24 UTC

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

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links