Template talk:Unbulleted list

src: multimixer.gr

Video Template talk:Unbulleted list

Unbulleted list

It appears that this template is not working properly. Therefore, a discussion was started to address this, as well as other problems, when used in Template:Infobox film. The current consensus is to remove this template in order to simplify editing and to allow the previous version used in the infobox template to be reimplemented. In case anyone was wondering, problems with the following browsers had shown bullets: IE 6,7, and 8, MSN, and Mobile Safari. Thanks for your time on this issue. ChaosMaster_Chat 21:20, 6 September 2010 (UTC)

It should be simple to fix this, but I lack the CSS skills to do so. The template uses the semantically correct and standards-compliant list markup. <br /> should not be used for such purposes. I've asked for help on VPT. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 21:57, 12 September 2010 (UTC)

Older browsers do not support list-style:none;. So there is no easy way to fix this other then to use <br /> instead, which we really don't need a template for. -- Edokter o Talk o 22:22, 12 September 2010 (UTC)

IE 6+ and Mobile Safari should support it, though. It seemed to work fine here in the Mobile Safari version I tried, and IE7 on Wine. Anomie? 01:08, 13 September 2010 (UTC)

IE has a bug where list-style:none doesn't override list-style-image: ..., at least in some circumstances. And the default CSS in both monobook and vector specifies a list-style-image. Consider these examples:

So if someone makes this edit, that may well fix the problem. I cannot test it in MSN browser, though, and Mobile Safari still does not show the issue in my tests with the iPhone Simulator. Anomie? 20:01, 13 September 2010 (UTC)

 Done. Cudos for finding that out... I looked it up and list-style is a compound attribute, so the image was indeed never reset. (But I still see no big advantage of using this over linebreaks). -- Edokter o Talk o 01:06, 14 September 2010 (UTC)

The image should have been reset, but since it's IE we're talking about it's not too surprising. Anomie? 01:17, 14 September 2010 (UTC)

Thank you, both. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 20:41, 14 September 2010 (UTC)

Maps Template talk:Unbulleted list

update to add missing numbers and expand to 50

Please update this template with the version in the sandbox. This update does two things, (1) adds number 20 which is missing, and is a serious bug! and (2) expand to 50 items for use in the article Interpol. Thank you. Frietjes (talk) 17:55, 6 May 2011 (UTC)

 Done. -- Edokter (talk) -- 18:32, 6 May 2011 (UTC)

src: multimixer.gr

Style parameter

The template allows a single parameter which, if present, applies that css style to each list element. I'd like to be able to change background-colour on an individual list element basis. Taking a simplified excerpt from List of Manchester United F.C. seasons

The entry for 1991 UEFA Super Cup should have the same coloured background (background-color:#FE2;") as the 1991 European Cup Winners' Cup Final, since Manchester United were winners in both cases. Passing the background-color as the li_style parameter to {{Ubl}} would incorrectly colour both list items - it's actually redundant as I can colour the whole cell gold if that's what was wanted.

If I try to use an inline style in a span, the template refuses to co-operate and loses the second entry:

So, should I create a derived template, say, {{Unbulleted list styled}}, modified to allow each entry an associated li_style_1, li_style_2, parameter? Or should we modify this template to perform that, given that the li_style parameter was undocumented until today, and it may not be in use? Is there any simple way of checking? Any other ideas (that don't involve using <br /> to create lists!) --RexxS (talk) 23:45, 25 August 2011 (UTC)

I don't see any problem with just adding individual "li_style_1", "li_style_2", ... to this template (as you have suggested). Frietjes (talk) 20:06, 26 August 2011 (UTC)

All done (though without the underscores before the numbers). -- Edokter (talk) -- 11:08, 27 August 2011 (UTC)

Many thanks. List of Manchester United F.C. seasons is indebted to you, and this will make it easier for other Featured Lists to meet modern standards of usability. I've updated the documentation to match. --RexxS (talk) 14:35, 27 August 2011 (UTC)

src: savvity.savvity.net

TfD

Please add {{TfD}}, per Wikipedia:Templates for discussion/Log/2011 December 27#Template:Unbulleted list. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:00, 27 December 2011 (UTC)

 Done. -- Edokter (talk) -- 23:42, 27 December 2011 (UTC)

src: cdn.auth0.com

Suggested move (February 2013)

src: multimixer.gr

Extra ul

When I look at the HTML output, I see an extra <ul>...</ul>:

--  Gadget850 ^talk 11:07, 8 September 2013 (UTC)

You're not supposed to include the '*'; this template only accepts list items as separate parameters. -- Edokter (talk) -- 12:19, 8 September 2013 (UTC)

we could make Module:Unbulleted list work like {{plainlist}} when there is only one input, but currently it does not per the documentation. Frietjes (talk) 18:04, 8 September 2013 (UTC)

Facepalm Nothing to see here, move along. Thanks. --  Gadget850 ^talk 19:57, 8 September 2013 (UTC)

It probably would be helpful if the Lua detected this situation, though. It seems probable that this will come up pretty frequently. -- SMcCandlish ? ? ¢ ?^???_??^?? 22:18, 5 September 2016 (UTC)

src: cdn.auth0.com

"nowrap" parameter?

{{helpme}}

I've noticed that this template is sometimes accompanied by the parameter |style=white-space:nowrap;, so I thought I'd try adding {{unbulleted list |nowrap |(etc)}} as a niftier alternative, but...

...with {{<includeonly>safesubst:</includeonly>#invoke:unbulleted list|unbulleted}} as the entirety of the template's code, I don't know how/where to begin!

Sardanaphalus (talk) 10:32, 17 March 2014 (UTC)

That woudn't work anyway, as |nowrap would be interpreted as the first list item. However, adding |class = nowrap has the same effect. -- Edokter (talk) -- 11:15, 17 March 2014 (UTC)

I was thinking of some code to detect whether {{{1}}} was "nowrap" and act accordingly, but |class=nowrap is still an improvement - thanks. Do you know where I may view a list of the classes available to Wikipedia editors? Sardanaphalus (talk) 12:49, 17 March 2014 (UTC)

What if the first item should actually show "nowrap"? We cannot use unnamed control parameter if they are already reserved for content. For a list of classes, see Wikipedia:Catalogue of CSS classes (it may be slightly outdated). -- Edokter (talk) -- 13:12, 17 March 2014 (UTC)

I reckoned it was (very) unlikely that the first item in a list would be "nowrap". (Even if so, I imagine there'd be a cunning workaround - using one or more HTML characters, maybe?) But |class=nowrap is all but as convenient. Thanks also for the Catalogue link; outdated or not, it looks useful. Sardanaphalus (talk) 23:16, 17 March 2014 (UTC)

"li_style[N]"

"li_style[N]" is ambiguous. Could this be made "li[N]_style", please? Sardanaphalus (talk) 09:54, 17 May 2014 (UTC)

That will break existing uses. We'd need a plan for that. -- Edokter (talk) -- 09:58, 17 May 2014 (UTC)

added here. Frietjes (talk) 14:47, 17 May 2014 (UTC)

Sorry, I reverted the addition of the new syntax. I don't mind which syntax is used, but I'd rather that only one is used, so that we can avoid unnecessary argument lookups. -- Mr. Stradivarius ^{? talk ?} 09:42, 18 May 2014 (UTC)

• New syntax, please. The ambiguity here may never become an issue, but in other templates it might (or already is), so let's remove this example. Sardanaphalus (talk) 10:09, 18 May 2014 (UTC)

• Again, existing uses. Please do some impact analysis first. I know this is used a lot. -- Edokter (talk) -- 11:01, 18 May 2014 (UTC)

so add a tracking category? I would do so, but I'm sure it would get reverted. Frietjes (talk) 14:00, 18 May 2014 (UTC)

Actually, I was thinking that a tracking category might be a good next step. -- Mr. Stradivarius ^{? talk ?} 14:16, 18 May 2014 (UTC)

so add a tracking category. I would do so, but I'm sure it would get reverted. Frietjes (talk) 17:06, 18 May 2014 (UTC)

• For the sake of future templates, much use sounds like much reason to amend the parameter numbering sooner rather than later. Can't bots be used to achieve this reasonably briskly before an amended syntax becomes the only syntax..? (With {{hlist}} too and other formatting templates that qualify?) Sardanaphalus (talk) 21:46, 18 May 2014 (UTC)

This discussion has reminded me of something that I've been meaning to do for a while - merge Module:Unbulleted list and Module:List. All the functionality of Module:Unbulleted list is actually included in Module:List already, including |li_stylen=. There is also a parameter |item_stylen=, which I included because I thought the concept of a "list item" would be easier to understand for non-coders than the concept of an "li tag". Taking this into account, we now have four choices for this parameter name - |li_stylen=, |lin_style=, |item_stylen= and |itemn_style=. Which would people prefer? Also bear in mind that we have separate |li_style= and |item_style= parameters. Personally, I'd like to get rid of all of the li parameters in favour of item parameters. -- Mr. Stradivarius ^{? talk ?} 10:58, 19 May 2014 (UTC)

I've now added a tracking category (Category:List templates with deprecated parameters) to Module:List/sandbox, as well as splitting apart the argument processing from the HTML rendering. At the moment all parameters containing "ol_style", "ul_style", and "li_style" are tracked (to be replaced with "list" and "item" parameters). I've also tracked "item_stylen" parameters, presuming that we want to replace them with "itemn_style" parameters. We need to work out what parameters we want before we put this up live, though. I'll adjust the code as necessary when we've decided what the names should be. -- Mr. Stradivarius ^{? talk ?} 13:12, 19 May 2014 (UTC)

• Thanks for your work, Mr. Stradivarius. I'd also felt that "ol"/"ul"/"li" were a bit on the cryptic side (unless, I suppose, for editors regularly using HTML) but thought moving the n should take precedence. If, though, "ol" etc are also up for change, my initial suggestions are:

i.e. along, I think, the lines you suggest. I hope I've understood the relationships between the parameters correctly. Sardanaphalus (talk) 21:03, 19 May 2014 (UTC)

|ol_style=, |ul_style= and |list_style= are all identical, so under my proposal |ol_style= would also become |list_style=. I'm not planning any change for the regular |style= parameter, as this is probably the most used, and the most of a pain to switch round. All of this depends on how large the impact of the changes would be, though, so it's not yet certain that we will make any changes. And I'm not so keen on "items_style" - "item_style" should be clear enough, and we can clear up any remaining confusion in the documentation. -- Mr. Stradivarius ^{? talk ?} 05:57, 20 May 2014 (UTC)

Centering text in a table

Hey, I'm trying to replace <br /> tags with this template and with the {{small}} template in a table with the text showing up centered.

Article is: Empire Award for Best Actor

Current code:

  | style="text-align:center"  | '''1996<br /> <small>[[1st Empire Awards|(1st)]]</small>'''  

What I tried doing:

  | style="text-align:center"  | '''{{unbulleted list|1996|{{small|[[1st Empire Awards|(1st)]]}}}}'''  

However the text is showing up on the left side. I'd appreciate help in solving this.--Gonnym (talk) 18:55, 8 May 2015 (UTC)

Looks like a conflict with the table CSS and the {{unbulleted list}} CSS. Try this:

  ! scope="row" | {{unbulleted list|1996|{{small|[[1st Empire Awards|(1st)]]}}}}  

You set the cell to be a header, then set the scope to row; thus it becomes a row cell with header styling, which is centered and bold. -- Gadget850 ^talk 19:11, 8 May 2015 (UTC)

Thanks, that works! One small visual problem now, the cell is now the color of the header and not the previous default color. Do you happen to know what the default color code is for "background:"?--Gonnym (talk) 19:22, 8 May 2015 (UTC)

Cells that contain data must not be marked up as if they were header cells (and vice versa), because of MOS:ACCESSibility. --Redrose64 (talk) 19:47, 8 May 2015 (UTC)

Ok I won't mark the cell as a header. Do you know how to fix the centering problem?--Gonnym (talk) 07:15, 9 May 2015 (UTC)

Why do you want to mark it up as a list anyway? Lists are typically used to group items that have a common theme, such as years: "1996" and "(1st)" do not have a common theme. --Redrose64 (talk) 09:02, 9 May 2015 (UTC)

Redundant div?

Why is this generating <div class="plainlist"><ul>...</ul></div> when <ul class="plainlist">...</ul> should suffice? -- SMcCandlish ? ? ¢ ?^???_??^?? 22:17, 5 September 2016 (UTC)

It's function p.renderList(data) in Module:List. Don't ask me how I found it. But as it's a module, I rather suspect that several templates use it, so one of those may need the enclosing <div>...</div>. --Redrose64 (talk) 23:13, 5 September 2016 (UTC)

Hmm. I don't even see the function itself in there, just a reference that something is being built for it. Anyway, I'll bring it up over there. -- SMcCandlish ? ? ¢ ?^???_??^?? 23:39, 5 September 2016 (UTC)

(Plain) horizontal display without the "dots"?

Using class=hlist will add "dots" in between items what {{hlist}} does. Is there a way to make the list horizontal while hiding these dots? Thanks. Sanglahi86 (talk) 15:06, 29 November 2016 (UTC)

Sanglahi86, yes, use |item_style=display:inline. if you want to prevent line breaks before/after the list, you may need |style=display:inline and |list_style=display:inline. -- Preceding unsigned comment added by Frietjes (talk o contribs) 16:24, 29 November 2016 (UTC)

Source of the article : Wikipedia