Last modified: 2014-03-02 20:13:23 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 T57830, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 55830 - Line breaking
Line breaking
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Lingo (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: s7eph4n
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-17 09:09 UTC by s7eph4n
Modified: 2014-03-02 20:13 UTC (History)
2 users (show)

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


Attachments

Description s7eph4n 2013-10-17 09:09:45 UTC
https://www.mediawiki.org/wiki/Extension_talk:Lingo#lqt_thread_id_32466, Lightbinder (talk), ‎21:39, 26 August 2013:

I've got Lingo 0.4.3alpha running on MediaWiki 1.21.2, and for most part it works great. There's a corner case, though, where if you have a term with spaces in it (e.g. myocardial infarction), and the line happens to wrap in the middle of the term, you end up with a tooltip that goes off the right margin of the page. I'm doing some investigation, but one quick-and-dirty fix for it is to add white-space: nowrap; to the .tooltip_abbr CSS class in skins/Lingo.css. That portion of my skins/Lingo.css, for instance, reads:

.tooltip_abbr {
  border-bottom: 1px dotted #bbf;
  white-space: nowrap;
}

This solves the problem, but it means that you can get some ugly line breaking patterns as a result. I'll keep investigating to see if there isn't a more elegant way to fix this bug.
Comment 1 s7eph4n 2014-03-02 20:13:23 UTC
Switched Lingo to use qTip, which does a pretty smart job in positioning the tooltip.

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


Navigation
Links