Last modified: 2007-03-06 18:24:37 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 9188 - text overflows template boundaries in print view in narrow browser
text overflows template boundaries in print view in narrow browser
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
PC Windows XP
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-03-06 17:22 UTC by David Fass
Modified: 2007-03-06 18:24 UTC (History)
0 users

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


Description David Fass 2007-03-06 17:22:56 UTC
The text in some templates appears (only in Print view) to overflow the template
borders when the browser width is made small.  For example, at
<>, there
is currently an "improve this article" template in the section "Songs of the
Suffering Servant".  When the browser width is decreased, the text in the
template overruns the template borders.  I suppose this should not happen, cause
it looks bad.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-03-06 18:24:37 UTC
The issue is that the long URL stretches the table cell, which makes the rest of
the text happily expand to the full width as well.  This has to do with table
sizing algorithms, which differ markedly from those for other elements; if the
contents were converted to use CSS (which would be doable although not
necessarily clean), the problem would not occur.  Regardless, this isn't really
something we can fix, it's a content issue.

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