Last modified: 2011-04-14 15:11:08 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 10276 - Sanitizer escapes "<p />" instead of allowing a blank paragraph through
Sanitizer escapes "<p />" instead of allowing a blank paragraph through
Status: NEW
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: need-parsertest
Depends on:
  Show dependency treegraph
Reported: 2007-06-15 15:33 UTC by David
Modified: 2011-04-14 15:11 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description David 2007-06-15 15:33:54 UTC
If an empty <p/> element is used in wiki markup, it's parsed as &amp;lt;p/&amp;gt; the resulting HTML, instead of an HTML paragraph element.
Comment 1 David 2007-06-15 15:34:55 UTC
Whoops.  I meant:



Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-06-20 06:36:10 UTC
Note that browser support for self-closing tags is, as far as I know, shabby, so it's probably best to translate it to <p></p>.
Comment 3 Jesse (Pathoschild) 2007-06-27 03:15:45 UTC
The paragraph element is a container, so a self-closing tag would probably make little sense in this case. The <br /> tag would be more appropriate, or correctly using the paragraph tag as a <p>container</p>, or using the wiki double-spacing syntax (which is parsed as <p> tags). 

It might be better to discourage the use of bad markup, rather than encourage it by hacking it into working.

Note You need to log in before you can comment on or make changes to this bug.