Template talk:Nepenthes

Page contents not supported in other languages.
Source: Wikipedia, the free encyclopedia.
carnivorous plants. For more information, visit the project page.
TemplateThis template does not require a rating on Wikipedia's content assessment scale.
Taskforce icon
This template is supported by WikiProject Plants.

scaling issue

This otherwise nice template does not scale well. I tried it with opera and firefox, and with both the font breaks out of the right border when the page is zoomed in. I changed the absolute 600px width to 40 em, this solves the problem for my browsers. Don't know about MS exploiter, though. --Sarefo 04:50, 20 November 2006 (UTC)[reply]

hm, very strange. although the template scaled nicely when trying it out in a sandbox, it was flowing over in its 'natural habitat' (Nepenthes pages). I enlarged the width to 48em, but have no idea what causes this double behavior. --Sarefo 05:01, 20 November 2006 (UTC)[reply]

Lists vs prose

I've just reverted the insertion of large number of the html <br /> into this template. A list is not a piece of prose broken up by line breaks as anyone using a screen reader will tell you. Wikipedia:Manual of Style/Accessibility #Lists clearly states "Do not separate list items with line breaks (<br />). Use one of the following methods ... Unbulleted lists ... Horizontal lists" --RexxS (talk) 20:13, 30 August 2012 (UTC)[reply]

Yes, and there is also the issue of
wp:deviations in the MOS which says to eschew all that raw html in favour of normal wiki-syntax. Anything with center and font tags is ripe for refactoring, anyway. I took things further, too; and the other way, too, by adding style=width:auto; which restores the width-per-content look that the prior implementation had. Br'er Rabbit (talk) 21:03, 30 August 2012 (UTC)[reply
]
looks good. the massive div/br version had text overflowing outside of the box on my browser. this version looks good. Frietjes (talk) 21:07, 30 August 2012 (UTC)[reply]
Much better, but we still have what is logically a single list broken up into multiple lists, solely for the purpose of creating arbitrary columns for visual presentation. Can we not avoid this? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:48, 30 August 2012 (UTC)[reply]