[wp-trac] Re: [WordPress Trac] #4716: <br /> tags added in inconsitent way

WordPress Trac wp-trac at lists.automattic.com
Fri Aug 10 09:46:10 GMT 2007


#4716: <br /> tags added in inconsitent way
---------------------+------------------------------------------------------
 Reporter:  hakre    |        Owner:  anonymous
     Type:  defect   |       Status:  reopened 
 Priority:  normal   |    Milestone:           
Component:  General  |      Version:           
 Severity:  normal   |   Resolution:           
 Keywords:           |  
---------------------+------------------------------------------------------
Changes (by hakre):

  * status:  closed => reopened
  * resolution:  wontfix =>

Comment:

 Replying to [comment:1 Otto42]:
 > You're seeing the effects of the autop filtering, which happens at page
 display time and not at post creation time. Carriage returns become br
 tags. Double carriage returns become P tags.

 I'll ignore the fact that it's quite useless to install a plugin to
 circumvent not working code. IGNORE.

 I can not confirm what you state here. If a \n or \r creates a <br/> well
 that's fine. And that's not the problem I was talking about. I was talking
 about the fact that applying <br/> elements is done in an inconsistent
 way.

 As you can see in my example <br/> elements are added in places where no
 \r or \n characters in the source exist. By '''source''' I mean the text
 typed in into the editor in the wordpress admin. That's the text that is
 written in the database. '''output html source''' is meant the rendered
 html that is send to the browser. this only for clarification.

 back to your argument that \r and \n will be converted to <br/>s. let's
 take my example:

 '''source:'''

 {{{
 <label>...</label><input ... />
 }}}

 will become the following '''output html source:'''
 {{{
 <label>...</label>
 <br/>
 <input ... />
 }}}

 If wordpress's autop would work the way you described, there should be no
 <br/>.

 you can add as many <br/>s as you like but it should be done in anycase
 the same way. not <br/> in one and nothing in another line. or popping up
 <br/>s out of nowhere. I repopened the bug therefore because what you
 wrote ignores the facts I was reporting.

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


More information about the wp-trac mailing list