Make WordPress Core

Opened 11 years ago

Closed 10 years ago

Last modified 10 years ago

#26608 closed defect (bug) (fixed)

/wp-admin/includes/post.php: Make HTML tag standard compliant

Reported by: latz's profile Latz Owned by:
Milestone: 4.2 Priority: lowest
Severity: trivial Version: 3.6
Component: Posts, Post Types Keywords: has-patch 3.9-early
Focuses: administration Cc:

Description

<br> tag isn't closed.

Attachments (1)

26608.diff (695 bytes) - added by Latz 11 years ago.

Download all attachments as: .zip

Change History (10)

@Latz
11 years ago

#1 @Latz
11 years ago

  • Keywords has-patch added
  • Severity changed from normal to minor

#2 @SergeyBiryukov
11 years ago

  • Keywords 3.9-early added
  • Milestone changed from Awaiting Review to Future Release
  • Priority changed from normal to lowest
  • Severity changed from minor to trivial
  • Version changed from trunk to 3.6

Related: [24042]

#3 @ocean90
11 years ago

What do you mean by "HTML tag standard compliant"?

Since we doesn't have a XML document here I'm fine with just <br>. There is really no need to "fix" such things.

See also http://www.w3.org/TR/html5/text-level-semantics.html#the-br-element.

#4 @Latz
11 years ago

You're right, I thought HTML5 would require properly closing all tags. Nevertheless there are the "WordPress Coding standards": Self-closing Elements (http://make.wordpress.org/core/handbook/coding-standards/html/#self-closing-elements). Secondly it's the only br tag in the whole code base that's not self closed. So at least it should be fixed for consistency.

#5 follow-up: @ocean90
11 years ago

Secondly it's the only br tag in the whole code base that's not self closed.

There are two more in JS files:

#6 in reply to: ↑ 5 @Latz
11 years ago

Replying to ocean90:

There are two more in JS files:

Does that mean you would support the ticket if those were changed, too?

#7 @jeremyfelt
11 years ago

  • Component changed from Administration to Posts, Post Types
  • Focuses admin added

#8 @wonderboymusic
10 years ago

  • Resolution set to fixed
  • Status changed from new to closed

Fixed via hackificator cleanup in [28497]

#9 @ocean90
10 years ago

  • Milestone changed from Future Release to 4.2
Note: See TracTickets for help on using tickets.