Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Double nested lists give bad output. #24

Closed
netcarver opened this issue Jan 30, 2011 · 2 comments
Closed

Double nested lists give bad output. #24

netcarver opened this issue Jan 30, 2011 · 2 comments

Comments

@netcarver
Copy link
Contributor

An example of invalid results from straight (though invalid) Textile:

## Red
## Blue

(Spotted by JSoo.)

@jsoo
Copy link
Contributor

jsoo commented Jan 31, 2011

As discussed on #textile (IRC), I would prefer Textile to ignore anything that is not valid Textile, and simply send it straight through. In this case:

<p>## Red<br />
## Blue</p>

Or in this case:

# Red
### Blue

Where current output is:

<ol>
    <li>Red
<ol>
    <li>Blue</li>
</ol></li>
</ol>

I would prefer:

<ol>
    <li>Red<br />
    ### Blue</li>
</ol>

@eliph
Copy link

eliph commented Dec 11, 2012

With Textile 2.4 I get:

<p> <ol>
    <li>Red</li>
    <li>Blue</li>
</ol></li></p>

for

## Red
## Blue

And this is fine, I believe. The HTML may be invalid, but the extra </li> tag will be ignored by any browser. Anybody seeking clean HTML code should clean up their Textile code first. And the HTML for

# Red
### Blue

is valid anyway, and probably is what the user wanted. So why bother?

@gocom gocom closed this as completed in 7b448d3 Nov 18, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants