Severity: Notice
Message: Undefined offset: 1
Filename: infosekolah/leftmenudasboard.php
Line Number: 33
Line Number: 34
Many thousands of Wikipedia articles have navboxes, in which lists of links are presented, horizontally, without using list mark-up, but instead using {{·}} or suchlike as a kludge. This is semantically poor and has implications for accessibility; not least as every {{·}} is read out as the word "bullet", to blind people using screen-readers.
{{·}}
To remedy that, a group of editors have collaborated to add to Common.css a class called hlist to which is now used by {{Flatlist}}. Here's a sample edit, adding it to a navbox. The visual output should be the same in all modern browsers; this has been widely tested.
hlist
The question now, is how best to apply the class to navboxes across Wikipedia? A bot job, obviously, but using {{flatlist}}, or some other mechanism? And are there any issues we should be aware of first? {{flatlist}} can be used with ordinary (UL) or ordered (OL) lists. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 18:37, 22 April 2011 (UTC)
{{flatlist}}
UL
OL
See also two related deletion debates. Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 19:10, 22 April 2011 (UTC)
Just wondering if it would be worth adding a |flatlist=yes parameter to the navbox template to allow for an option of making all the lists use the hlist class. -- WOSlinker (talk) 20:22, 22 April 2011 (UTC)
|flatlist=yes
For example:
{{Navbox/sandbox |navbar=plain |title = Example |group1=Group 1 |list1= *Item 1 *Item 2 *Item 3 *Item 4 *Item 5 *Item 6 *Item 7 *Item 8 |group2=Group 2 |list2= *Item 1 *Item 2 *Item 3 *Item 4 *Item 5 *Item 6 *Item 7 *Item 8 }}
How can we move this forward? Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 21:56, 27 April 2011 (UTC)
Any news? Andy Mabbett (User:Pigsonthewing); Andy's talk; Andy's edits 14:13, 17 May 2011 (UTC)
|vlist=yes
|listn=
<div>...</div>
If I don't hear any more on this in the next few weeks, I'll see about adding a flatlist param. -- WOSlinker (talk) 08:30, 23 October 2011 (UTC)
The use of |child= causes an HTML validation error, for example {{navbox}} Renders as
|child=
{{navbox}}
Which cause an error on this page; see W3C markup validation for Template talk:Navbox. ---— Gadget850 (Ed) talk 01:45, 24 August 2011 (UTC)
<ul>
end tag for "table" which is not finished
There's a watered down version of this template in the spanish wiki, but in order to use the "subgroup" template, you must have the english wikipedia code of the navbox template. I've been trying to copy and paste the code from this wikipedia, to the spanish wiki. It works, sort of though... here's an examlple: es:Plantilla:Navegación/núcleo2/test, I haven't figured out yet what's not working properly... and I can't seem to fix it. The "subgroup" template in the spanish wiki is a direct copy from the english wiki... so basically both the navbox and subgroup codes are identical (I deleted the navbar code, but even if left on, the same problem occurs).
Navbar code in the spanish wiki: es:Plantilla:Navegación/núcleo2 Subgroup code in the spanish wiki: es:Plantilla:Navegación/subgrupo.
The code I'm using in the "test" is also a direct copy from the enlgish wiki.
Am I doing something wrong? Or is it that the spanish wiki doesn't support some parts of the code? Thanks for your time. --MindZiper (talk) 00:31, 26 September 2011 (UTC)
A template I watch was recently converted to flatlist. When viewed in any version of IE, it creates several problems, most notably the major misalignment of the dots and the addition of an extra dot after the end of the list (example below). Can anyone help solve this? Unfortunately the only answers I've had so far is to question why I've chosen to use the wrong browser (IE, the most commonly used one in the world), to have to switch to compatibility view (which works, but I don't see why readers should have to do this, and it isn't available on older versions of IE), and to say that Microsoft should solve the problem. In the meantime I've been told to just put up with the problem rather than revert to the issue-free version - is this acceptable? Number 57 08:55, 1 October 2011 (UTC)
:last-child
.hlist li ul { display: inline; }
* book title (year)
.hlist li { white-space: nowrap; }
I've had a good search to see how the javascript modules do the job of emulating :last-child. After much trial and error in my monobook.css, I have a slight improvement available for IE8 in compatibility mode:
.hlist li {background-image: expression(this.nextSibling==null?'none':'');} .hlist li {padding-right: expression(this.nextSibling==null?'0em':'0.4em');} .hlist li {margin-right: expression(this.nextSibling==null?'0em':'0.2em');}
You can paste it into your own local css and see how (badly) it works in your version of Internet Explorer. Without compatibility mode, IE8 displays cleanly, but with the dot at the end of each list as before. In compatibility mode, IE8 evaluates the 'expression' syntax and clears the final dot. Other browsers ignore that, so are unaffected by the declarations. I've had to jigger the right-padding & right-margin to make it look similar to other browsers, but sadly IE8 in compatibility mode doesn't maintain a right-padding against the right border of a container, so it may squash the dot into the text at the end of each line that wraps. Ugly, but that's MS for you. It would be interesting to see how this shows up in IE9 in compatibility mode, but I haven't checked yet. --RexxS (talk) 00:15, 2 October 2011 (UTC)
Hi. I have been referred here by User:Frietjes re: Template:Roy Harper which has recently become illegible on my browser (IE8). All other templates fit my screen fine, there are 4 here (Jimmy Page) that are perfect. So, can anyone fix this? I am at the limit of my abilities, creating the template was hard enough and if it wasn't broken, why fix it? Thanks. Stephenjh (talk) 09:03, 12 November 2011 (UTC)
I've added one line of javascript to Common.js that at least removes the trailing dot from the last list item in IE 6, 7 and 8. So far, nothing I can do about the misallignment of the dots in IE8's compatibility mode. — Edokter (talk) — 17:00, 24 October 2011 (UTC)
May I refer fellow editors to Semantic and accesssible list markup, above which seems to have stalled? Andy Mabbett (Pigsonthewing); Andy's talk; Andy's edits 19:42, 15 October 2011 (UTC)
To eliminate duplication of content, I made a few child navbox templates that integrated into parent templates like this:
However, the columns weren't perfectly aligned, so another user copied and pasted the child templates back in. Is there some way we could get both features at the same time? --Joy [shallot] (talk) 17:06, 26 October 2011 (UTC)
Hi, template edits made here and here with summary like "update to best practice" have messed up the formatting, at least in IE8. Example "before and after" screenshots from IE are here. As you can see, while the old version is fine, the bullets, or interpuncts, or whatever they are, look horrible in the new version.
Unless there are worse problems with the old format that I am not seeing (e.g in other broswers), my feeling is that these changes need to be undone wherever they have been implemented, and any claim anywhere that they are "best practice" needs to be removed. I am raising it here in case it is a widespread problem or problem in the making. Regards, 86.177.108.207 (talk) 03:35, 10 November 2011 (UTC)
<meta http-equiv="X-UA-Compatible" content="IE=edge">
I have added the listclass parameter. This will eliminate the need for using {{flatlist}}. The only thing needed to produce horizontal lists is to add {{{1}}} to your navbox, and it will automatically format the list cells as horizontal lists. — Edokter (talk) — 09:07, 10 November 2011 (UTC)
The wrapping issues noted by Jayron32 and others are due to IE's "Compatibility" view (irony intended). The reason why bodyclass seemed unaffected is because of a (now fixed) CSS coding mistake. At the moment, {{flatlist}}, bodyclass and listclass in navboxes now all produce the same broken wrapping behaviour in Compatibility view. There is only one solution: turn off Compatibility view for Wikipedia. — Edokter (talk) — 12:09, 11 November 2011 (UTC)
An editor comment to me that he's seeing {{campaign}}-boxes widen when [show]n, when in IE's do-it-wrong-mode (my term). Seems to me that their old-school mode might be getting the recent white-space: nowrap; tweak inadvertently applied to the ul/ol elements. If so, something like:
.hlist ol, .hlist ul { margin: 0 !important; white-space: normal; // for old-ie-modes? }
might help. Might help to use !important, too. Alarbus (talk) 05:01, 12 November 2011 (UTC)
.navbox .hlist li { white-space: nowrap; }
Here's a screenshot if it helps. Nightw 16:05, 12 November 2011 (UTC)
Could I request that when editors and readers come forward with complaints about flatlist, that certain editors stop telling them to change their internet browser or switch to compatibility mode? This is the least helpful response possible, and is incredibly patronising - trying to switch the blame for the fault to the reader is not really fair. Whatever people's opinions of IE, it is the most widely used browser in the world, and the solution should be to make it work with IE. Number 57 11:29, 12 November 2011 (UTC)
Whatever one's opinion of IE is, the fact remains that it is widely used by readers—whether it's 34% or 10%, that's alot of readers. While you're busy telling everyone that comes here what the problem is and where the button is to fix it, please realise that for everyone that comes here there are probably a hundred casual readers out there that will not know what's causing the problem. No, readers should not be asked to do anything, but that's not the main issue here. It might be if readers were being made aware of what was causing the problem, but most of them will never know and the problem will remain. Until an appropriate discussion is had over the affects of this change and an adequate consensus is achieved, I'm reverting the changes on the templates that I watchlist. Nightw 13:15, 12 November 2011 (UTC)
I've no idea if this is the right place to ask this question, please advise if not.
The middot is implemented using , i.e. File:Middot.png. But, on my screen this picture is significantly uglier than • , i.e. {{•}}, or · , i.e. {{·}}, because a PNG is not a vector image that can scale to e.g. 18px. To reproduce in Firefox, press Ctrl + a few times.
Can this be fixed? Use SVG, or even simply the characters • or ·? --Joy [shallot] (talk) 10:59, 12 November 2011 (UTC)
content: " ·"; font-weight: bold;
|answered=
Last edit should be undone (or corrected). Its include {{#if:{{{name|}}}|{{Navbar/sandbox|{{{name}}} which means a lot of page now includes Template:Navbar/sandbox. Christian75 (talk) 12:37, 7 December 2011 (UTC)
