= Description =
Text on subsequent lines in a numbered list item with same indent level is not considered part of same paragraph.
== Example ==
=== Indented text ===
Markup
{{{
first line
subsequent line
first line
subsequent line
first line
subsequent line
}}}
Display:
first line
subsequent line
first line
subsequent line
first line
subsequent line
Works as expected.
=== Unordered list ===
Markup:
{{{
* first line
subsequent line
* first line
subsequent line
* first line
subsequent line
}}}
Display:
* first line
subsequent line
* first line
subsequent line
* first line
subsequent line
Generated HTML:
{{{
}}}
Works as expected.
=== Ordered list ===
Markup:
{{{
1. first line
subsequent line
1. first line
subsequent line
1. first line
subsequent line
}}}
Display:
1. first line
subsequent line
1. first line
subsequent line
1. first line
subsequent line
Generated HTML:
{{{
-
first line
-
subsequent line
-
first line
-
subsequent line
-
first line
}}}
Broken, spacing is broken, too. I think this should use this markup instead:
{{attachment:ordered-list.html}}
== Details ==
This wiki
== Workaround ==
## How to deal with the bug until it is fixed
Use long lines in ordered lists.
= Discussion =
How should it then know when to start a new enumbered list by 1? A list item is different in this case. The example shows a long line in the editor but not on screen.
1. do this...
1. then this<
>like this
1. and finally this
-- ReimarBauer <>
This is not the problem - the user want to use hard warping of paragraph text in editing, but get one paragraph in the end.
This is NOT a duplicate of ../BlockElementsInListBreakIndent :) . Text on subsequent lines with same indentation should be treated as same paragraph - just like it seem to works in bulleted lists. We should check the parser, this may be a simple indent calculation error.
The docs described that this should work. I updated the docs to reflect the current code, when we fix this, we should remove the note in the docs.
-- NirSoffer <>
= Plan =
## This part is for Moin``Moin developers:
* Priority:
* Assigned to:
* Status: fixed in moin--refactor--1.5 branch...
----
## When the bug is fixed, replace the category to Category MoinMoinBugFixed
## If this is not a bug, replace with Category MoinMoinNoBug
CategoryMoinMoinBugFixed