Opened 15 months ago
Last modified 15 months ago
#20120 new enhancement
Space before slash to close BR
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Formatting | Version: | 3.4 |
| Severity: | trivial | Keywords: | |
| Cc: |
Description
Kind of a petty, I admit, but I noticed http://codex.wordpress.org/WordPress_Coding_Standards shows this as the standard, and I figured I'd help out by checking if any such occurrences exist (using the following):
find -name '*.php' -type f | xargs egrep -n "<br\/>"
Diff attached (my first)...but I won't have my feelings hurt if the ticket is closed and I am banned from trac :)
Attachments (1)
Note: See
TracTickets for help on using
tickets.
The W3C document that WP CS guideline was written 12 years ago - I've been trying to find out a definitive list of the "older browsers" are that everyone refers to when saying the space is needed for their compatibility.
If, as some say, it's for Netscape Navigator (4), and earlier, then the space could probably be dropped.
I've even tweeted at Hixie and Eliot Graff (author of the HTML-XHTML Polyglot document to see if they have a list.
I think it may end up with finding someone with an afternoon free who can install old versions of all the browsers and a simple test page to determine which browsers don't display <br/> correctly.