Last modified: 2010-05-15 15:33:41 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 1569 - HTML comments in wikitext can cause extra spaces in rendered HTML
HTML comments in wikitext can cause extra spaces in rendered HTML
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
1.4.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
http://en.wikipedia.org/wiki/Madge_Ob...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-02-21 05:00 UTC by Jeff Bonham
Modified: 2010-05-15 15:33 UTC (History)
0 users

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


Attachments

Description Jeff Bonham 2005-02-21 05:00:19 UTC
Wikitext such as: 
 
Madge then purchased mercuric chloride tablets under the guise of shopping for 
something else, <!-- my sources disagree whether it was a hat or makeup --silsor --> 
and consumed them in another attempt at [[suicide]]. 
 
can result in two spaces being visibly rendered in the HTML, one of which is a 
&#160; as follows: 
 
Madge then purchased mercuric chloride tablets under the guise of shopping for 
something else,&#160; and consumed them 
 
This is a bug because the default behaviour of HTML rendering agents is to ignore 
extra whitespace, but the presence of the &#160; prevents this.
Comment 1 Antoine "hashar" Musso (WMF) 2005-07-09 18:11:51 UTC
This is fixed in cvs.

There is still a double space cause there is one before and after
the comment block which is correct behaviour. &#160; no more
generated.

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


Navigation
Links