![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 19 years ago
Closed 2 years ago
#5250 closed defect (bug) (wontfix)
wpautop() issue with lists
| Reported by: | Narc0tiq | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Formatting | Version: | 2.3 |
| Severity: | normal | Keywords: | needs-patch needs-unit-tests wpautop |
| Cc: | Focuses: |
Description (last modified by )
First of all, my sincere apologies if this is a duplicate.
The problem, in short: WordPress inserted a number of unclosed <p> tags into my post. It should either insert correctly closed tags, or none at all. I honestly would prefer the former.
In detail: I had HTML code very similar to this:
<ul>
<li>text<ul>
<li>subtext</li>
</ul>more text</li>
</ul>
This was automatically converted to:
<ul>
<li>text<ul>
<li>subtext</li>
</ul><p>more text</li>
</ul>
Note the extra <p> tag in the above, which is unclosed (making the W3C validator choke on my website).
Also note, I was not using the WYSIWYG editor (turning it off was the first thing I did), so it's unlikely to be due to that.
As a workaround, manually inserting properly closed <p> tags works just fine:
<ul>
<li>text<ul>
<li>subtext</li>
</ul><p>more text</p></li>
</ul>
Since this workaround exists, the bug is not very prioritary, but it should also (hopefully) be easy to fix.
Change History (17)
#2
@
19 years ago
- Keywords autop added
- Milestone → 2.4
- Priority low → normal
- Severity trivial → normal
#4
@
19 years ago
- Keywords needs-patch added; xhtml autop removed
- Summary Unclosed p tags -- not XHTML-compliant! → wpautop() issue with nested lists
I take that back. I forgot the text after the first </ul> and even with more line breaks, it added in a <p>. My apologies.
#9
@
15 years ago
- Summary wpautop() issue with nested lists → wpautop() issue with lists
This looks related to a test case I was preparing to demonstrate how flawed the output from wpautop can get inside lists:
<ol> <li> foo bar </li> </ol>
renders as:
<ol> <li> foo</p> <p>bar </li> </ol>
whereas I'd expect it to be
<ol> <li> <p>foo</p> <p>bar</p> </li> </ol>
I'm changing the summary to generally cover wpautop's problems within <li> elements.
#12
@
11 years ago
- Keywords needs-unit-tests added; xhtml wpautop removed
- Milestone Future Release
- Resolution → wontfix
- Status new → closed
Closing as wontfix. Complete lack of interest on the ticket over the last 4 years. Feel free to reopen when more interest re-emerges (particularly if there's a patch)
#14
@
11 years ago
- Keywords wpautop added
- Milestone → Future Release
- Resolution wontfix
- Status closed → reopened
#15
follow-up:
↓ 16
@
3 years ago
- Keywords close added
Tested with 6.2 alpha:
<ol> <li> foo bar </li> </ol>
Generates:
<p><ol> <li> foo bar </li> </ol></p>
I think that is right and fine as behavior.
Another work around is just to add in some line breaks: