Last modified: 2011-07-13 20:36:44 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T13312, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 11312 - URL with hyphen in Infobox displays improperly with unintended break
URL with hyphen in Infobox displays improperly with unintended break
Product: MediaWiki
Classification: Unclassified
Parser (Other open bugs)
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-09-12 15:32 UTC by Kent
Modified: 2011-07-13 20:36 UTC (History)
1 user (show)

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


Description Kent 2007-09-12 15:32:52 UTC
In the Infobox under this entry, a link to Jane Wyman's official website is given.

The display of the URL breaks at the hyphen, putting the URL on two lines, but also displays a corrupted outside link icon after the URL.  The icon looks like it's either broken in two pieces or is missing a portion of it (perhaps obscured by some white space).  The link itself is functional, in that it does take you to the correct page.  The icon part is not functional as a link.

Without the dash, the URL and icon display perfectly (but, of course, won't take you to the correct site).
Comment 1 Brion Vibber 2007-09-13 15:33:07 UTC
Some browsers do line breaks at "-" while others don't.

If you wish to enforce non-breaking, you can wrap it in <span style="white-space: nowrap">...</span> or equivalent template.
Comment 2 Dan Collins 2011-07-13 20:36:44 UTC
This is a difference in various browsers which is outside our control. We certainly don't want to make links white-space: nowrap by default, so Brion's solution works fine as a workaround where the problem exists. Not a bug on our side, so closing as invalid.

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