[wp-trac] Re: [WordPress Trac] #2259: autop creates unclosed paras inside list items

WordPress Trac wp-trac at lists.automattic.com
Thu Feb 1 17:55:33 GMT 2007


#2259: autop creates unclosed paras inside list items
--------------------------+-------------------------------------------------
 Reporter:  Viper007Bond  |        Owner:  anonymous
     Type:  defect        |       Status:  reopened 
 Priority:  low           |    Milestone:  2.2      
Component:  General       |      Version:  2.0      
 Severity:  minor         |   Resolution:           
 Keywords:                |  
--------------------------+-------------------------------------------------
Comment (by priv):

 In 2.1 the autop are more insane.

 Following source:

 {{{
 <ul>
 <li>Item 1, Paragraph 1<br /> <br />Item 1, Paragraph 2</li>
 <li>Item 2, Paragraph 1<br /> <br />Item 2, Paragraph 2</li>
 </ul>
 }}}

 after apply filter will also become
 {{{
 <ul>
 <li>Item 1, Paragraph 1
 <p>Item 1, Paragraph 2</li>
 <li>Item 2, Paragraph 1
 <p>Item 2, Paragraph 2</li>
 </ul>
 }}}

 You don't have chance to add a newline in the list without break html.

 And also, seems now 2.1 eat up any amount of br tags and newlines, and
 results in p tags.

 The only way to get extra space is {{{<p>&nbsp;</p>}}}, and don't think of
 use it in the list, since it will create a three-line space.  Oh, wait,
 maybe we can turn off the space between paragraph by inline css.

 I must say the autop guys are really hate br and newlines, aren't they?

 More worse, in 2.1 they're trying to strip the {{{<p>}}} structures
 created by TinyMCE before saving(to tidy the result??), so the output will
 have no choice but rely on autop.

 If the filter will stay as a set of regexp and won't become a full parser,
 please don't do too much of the 'smart things', ridiculous.

-- 
Ticket URL: <http://trac.wordpress.org/ticket/2259#comment:10>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list