This template is within the scope of WikiProject Lists, an attempt to structure and organize all list pages on Wikipedia. If you wish to help, please visit the project page, where you can join the project and/or contribute to the discussion.ListsWikipedia:WikiProject ListsTemplate:WikiProject ListsList
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. ChaosMasterChat21:20, 6 September 2010 (UTC)[reply]
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 edits21:57, 12 September 2010 (UTC)[reply]
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 • Talk • 22:22, 12 September 2010 (UTC)[reply]
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)[reply]
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:
This sets list-style-type:none, and shows a bullet in Firefox and IE
This sets list-style:none, and shows no bullet in Firefox but does in IE
This sets list-style:none none, and shows no bullet in IE in my tests
This sets list-style-type:none;list-style-image:none, and shows no bullet in IE in my tests
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)[reply]
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 • Talk • 01:06, 14 September 2010 (UTC)[reply]
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
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)[reply]
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
Season
Europe
1990–91
Cup Winners' Cup – Winners
1991–92
Cup Winners' Cup – Round 2
Super Cup – Winners
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:
Season
Europe
1990–91
Cup Winners' Cup – Winners
1991–92
Cup Winners' Cup – Round 2
Super Cup – Winners
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)[reply]
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)[reply]
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.A summary of the conclusions reached follows.
oppose, this list format has two major features (1) vertical and (2) without bullets. given that the standard list format in html is both vertical and with bullets, the distinguishing feature here is that it is without bullets. the vertical aspect is not special. Frietjes (talk) 18:00, 12 February 2013 (UTC)[reply]
But, (1) when compared with its complementary hlist/flatlist/etc, you don't find their respective alignments the greater difference?; (2) hlist/etc characteristic of Navboxes etc, i.e. horizontally-orientated templates, while plainlist/unbulleted list/etc characteristic of Sidebars etc, i.e. vertically-orientated templates..? CsDix (talk) 19:00, 12 February 2013 (UTC)[reply]
as I said, the standard list is (1) vertical and (2) with bullets. hence, a horizontal or flat list deviates from the standard in that it is horizontal or flat, which is why we call it a horizontal or flat list. this list deviates from the standard in that it is without bullets or plain, hence we call it an unbulleted list or a plain list. Frietjes (talk) 19:30, 12 February 2013 (UTC)[reply]
Thanks for reminding me about the bullets / no-bullets distinction. I wonder if the first and foremost distinction should be between the horizontal and vertical, but, for now, is there a correct way in which I may cancel this rename request? CsDix (talk) 21:19, 12 February 2013 (UTC)[reply]
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)[reply]
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!
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
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:
style→[unsure]
ul_style→list_style [although maybe the current style should become list_style..?]
ol_style→numlist_style..?
li_style→item_style [and/or items_style, as it applies to all items..?]
|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)[reply]
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.
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. --Gadget850talk19:11, 8 May 2015 (UTC)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
I used {{ubl}} in a template, and I see this effect in mobile view:
In mobile, the browser adds an invisible bullet (as in: bulleted list). The bullet is invisible, but does take whitespace (visual indenting). This happens on my mobile browser (iPhone) and the wikipage-show-mobile option (in-desktop mobile view). Actually, when the page is being visually rendered, for a moment the bullets show.
At Imagen Ltd, I wrapped the list of key people in the infobox in an unbulleted list template. The line for "Tom Blake, Commercial Director" wrapped to a second line, left-aligned with all the items in the list, leaving the continuation line visually indistinct from the first line of a new list item. For clarity, I added item_style=text-indent: -1em; margin-left: 1em; to add a hanging indentation, which pushes an item's continuation lines to the right by 1em. What would people think of making hanging indentation part of the standard formatting for this template? Largoplazo (talk) 11:21, 23 March 2018 (UTC)[reply]
@Jay D. Easy:Thanks for that. Now that you've reminded me of my question, it occurred to me to make this a formal edit request, since I do think this should be done here, so I've now posted one below. Largoplazo (talk) 12:22, 5 December 2019 (UTC)[reply]
Template-protected edit request on 5 December 2019
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Oh, I don't know. I just took what was already at {{unbulleted list/sandbox}} (which I now see references the list/sandbox module instead of the list module), assuming without thinking about it that it was identical to {{unbulleted list}}, and added the item_style parameter. I wasn't relying on any difference between the List and List/sandbox modules.
This has quite a wide-reaching impact; shouldn't such a change have been discussed first? For example, this change creates inconsistencies between line wraps of UBL items and those of single-liners (which are not indented). Personally, I also find it very unappealing to the eye. Lordtobi (✉) 21:29, 8 December 2019 (UTC)[reply]
Also regard these test cases where the change deviates the original style (in this case, the sandbox resembles the original version):
I don't have time to look at your review and example right now, but re "shouldn't such a change have been discussed first?": it was up for discussion for over a year and a half. Largoplazo (talk) 15:55, 9 December 2019 (UTC)[reply]
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
Warning: I stand with Lordtobi on this. This request was too hastily approved and I urgently implore that it be reverted immediately, as this may indeed have far-reaching consequences in its current form. As shown in the example above, this mode of item indentation is certainly not free of error. In #Hanging indentation on list items I mentioned I made {{indented plainlist}} and {{unbulleted indent list}}. These also exhibit the very same issue. Certainly not every infobox agrees with their transclusion, and in some it causes data field output to be thrust into its corresponding label field, also evidenced by the example shown above.
I strongly recommend using {{indented plainlist}} and {{unbulleted indent list}} to create indented-item lists until such time as these are proven to be error-free. Both can be turned into redirects to {{plainlist}} and {{unbulleted list}} at some point, as both invoke Module:List. Next to that, if and when it is decided to include support for item indentation in {{unbulleted list}}, it would be much more preferable for it to be customizable, and more importantly, for it to be optional instead of enabled by default, as is currently the case. Jay D. Easy (t • c) 16:54, 9 December 2019 (UTC)[reply]
Reverted. Please continue discussion and experimentation in the sandbox. I encourage test case editors to copy the cases above, especially the ones with colored backgrounds, into the testcases page. – Jonesey95 (talk) 17:32, 9 December 2019 (UTC)[reply]
I thought it was easier to read the page in source mode when the infobox uses {{ubl}} since {{unbulleted list}} is very long when it appears many times in one infobox. Also, almost every article I’ve come across uses {{ubl}}. Interqwarktalkcontribs08:15, 4 June 2018 (UTC)[reply]
I prefer {{ubl}} for the same reason. Brevity, simplicity. Frankly annoying when someone reverts it to {{unbulleted list}}. I also move full sources down to Template:Reflist because it makes the source WAY easier to read and edit. Cognissonance (talk) 18:16, 4 June 2018 (UTC)[reply]
@Cognissonance: That is two unrelated issues. The first - whether to use {{unbulleted list}} or {{ubl}} - is merely one of whether to use the true name of the template or a redirect that does exactly the same job in fewer characters. The second (I presume that you mean altering the article to use list-defined refs) is a change to the ref style and per WP:CITEVAR should be discussed first. --Redrose64 🌹 (talk) 22:49, 4 June 2018 (UTC)[reply]
Why does this template have an extra space in between list items in the mobile version of Wikipedia (when compared with making pseudo-lists with <br>)? Ezhao02 (talk) 00:20, 22 July 2020 (UTC)[reply]
Centering text in a table: answer
After some trial and error I found the answer to the 2015 question above, as illustrated here...:
Wikitable with {{yes}} or {{no}} style on each row (background-color and text-align:center) to illustrate style interference and how to fix it
Code
Output
Centered very very very very very very long string of text
Centered very very very very very very long string of text
Centered short text
Centered short text
{{Unbulleted list|Items are left aligned|{{tl|Unbulleted list}} default style overrides {{tl|no}} style}}
Div-span-error is thrown when ubl is used in Infobox Book
I'm finding an issue with ubl in infobox book. When ubl is used in infobox book on the parameter "title_orig", it throws a div-span-flip error which WP:LINTMiscellaneous issues keeps finding when ubl is added to the page in question, The Sound of the Mountain.
Anyone have an idea why these two are not compatible? It visually works, yes, but not without the div-span-flip error being thrown.
Zinnober9 I don't get the mentioned error on my Yosemite Mac, and haven't in the past, so I was wondering what you meant. Have you tried using "unbulleted list" instead of "ubl"?--Robert Kerber (talk) 18:26, 22 June 2021 (UTC)[reply]
@Robert Kerber: Since {{ubl}} is simply a redirect to {{Unbulleted list}}, switching to the latter won't make a scrap of difference. The offending HTML is:
Putting a div inside a span is not permitted. The problem is not with {{ubl}}, but with {{infobox book}}, since it is the latter that produces the <span lang="ja" style="font-style: normal;" title="Japanese-language text">...</span>. --Redrose64 🌹 (talk) 23:27, 22 June 2021 (UTC)[reply]
Unbulleted lists with nested bulleted lists
This is a situation that crops up frequently in infoboxes. I want a nested list with the top level unbulleted and the subordinate list bulleted. Unfortunately nesting {{unordered list}} inside {{ubl}} (or {{ubli}}) produces a visually flat list, because there are no bullets or indentation due to it inheriting the list-style-type and margin-left:
{{ubl|Foo{{unordered list|Bar|Baz}}|Quux}}
Foo
Bar
Baz
Quux
To get the desired display, you have to force both list-style-type and margin-left:
In my opinion, subordinate lists built with {{ubl}} should not inherit the enclosing list's bullet type, and definitely should not inherit indentation. {{unordered list}} should always add bullets (unless you explicitly disable them). Hairy Dude (talk) 15:18, 3 June 2024 (UTC)[reply]
I would far prefer to see children within an unbulleted list stay unbulleted:
You could do something with classes to get around it, but out of the million plus articles using this template, some may have intentional layers of unbulleted lists. Rjjiii (talk) 02:31, 4 June 2024 (UTC)[reply]