Last modified: 2008-10-21 00:52:31 UTC
The idea is to allow us to present only a few references, and allow the user to scroll down to see the rest. In the Hebrew Wikipedia we use a DIV tag around the <references /> tag to style it. See http://he.wikipedia.org/wiki/%D7%99%D7%92%D7%95%D7%90%D7%A8 for an example (at the end of the article). You see, it would be easier if we could just add styling like this: <references style="border: 1px solid black;" /> Also, an scroll overflow would be nice too, so that this can be done: <references style="border: 1px solid black; overflow: auto; height: 160px;" /> Or better yet: The height will be defined by an input number that represents the number of references: <references style="border: 1px solid black; overflow: auto;" maxref="5" /> i.e. only 5 references are visible and in order to view the rest you need to scroll down. OR - if possible - only 5 references visible and in order to view the rest you need to click the "Show" link. If you can create a "maxref" option - it would be best if we could enter this as a parameter in a template: <references style="border: 1px solid {{{color|black}}}; overflow: auto;" maxref="{{{maxref|5}}}" /> Thanks, Yoni
References could be styled globally in MediaWiki:Common.css or such style CSS (like MediaWiki:Monobook.css). However passing the overriding direct style (as well as classnames) could make things easier although styling via wrapping div is working solution. On the other hand - additional scrollbars are against accessibility and usability guidelines - don't use it. Let the user decide, how he wants to display it - that's why custom stylesheets are available. Setting the reference box height by number of references is impossible - user agents can't determine these things. The only possibility would be "counting" of lines (via setting the box height to the appropriate multiple of line heights). Collapsible reference box can be set via custom JavaScript in MediaWiki.Common.js.
This bug is very similar to (possibly even a duplicate of) bug 6019.
*** This bug has been marked as a duplicate of bug 6019 ***