Template talk:Bar percent

message: I can't get it to work on a MediaWIki installation - I had to delete all table syntax wrapping the parser functions (or how do you call it) because it was showing up raw after saving the page and now I have bare bars - I have all sorts of parser extensions and css classes set up and everythig else from wikipedia pretty much works.
Does the table syntax in this template use some advanced fonctionalities I might not have installed?  354d 18:47, 11 October 2007 (UTC)

message: Please change:
 width:100px
to
 width:100px
The problem here is that while  has a parameter to adjust the width of the bar area, the actual bar (which is generated by this template) is fixed at 100px. This change adds a parameter to manually change the width here as well. See Template talk:Bar box for details on how these templates work. PC78 (talk) 23:29, 19 February 2009 (UTC)
replies: text: Done. Cheers.--Fuhghettaboutit (talk) 23:46, 19 February 2009 (UTC)
thread_title: Edit request

message: Please replace:



  
0%




with



  
0%




for HTML5 compliance.  Thank you. —  (e • t • c) 19:53, 4 December 2014 (UTC)
replies: text: (i) Why paste code blobs here when you have made what I presume are the appropriate changes in the template's sandbox? (ii) What is non-compliant about (a) the colour values silver and gray; (b) the lack of spacing in the style= attributes? Sifting carefully through this maze shows me that the only change that is truly for HTML5 compliance is the replacement of one align="right" attribute with the CSS declaration text-align: right;. --Redrose64 (talk) 20:34, 4 December 2014 (UTC)
replies: text: The changes for color names to hex values is for consistency as not all browsers rendered named colors exactly the same, spacing changes are for readability of code, and yes, the only "technical" HTML5 compliance change is eliminating the align=right in favor of the css equivalent.  The changes requested are as I would have made them.  Whomever carries out this request, please make the changes as you see fit as long as the goal of this request is realized. Thank you. —  (e • t • c) 20:52, 4 December 2014 (UTC)
replies: text: There shouldn't be any browser inconsistency in the colour values, because they are defined in CSS 2.1 and CSS Color Module Level 3. --Redrose64 (talk) 21:22, 4 December 2014 (UTC)
replies: text: https://developer.mozilla.org/en-US/docs/Web/CSS/color_value says that earlier version of IE don't support all named colors.  Especially (.*grey.*) colors.  Using hex instead promotes consistency. —  (e • t • c) 22:09, 4 December 2014 (UTC)
replies: text: It says that the keywords colours (which include gray and silver) work with IE 3.0 on. It also states "the 'e'-grey colors (with an e) (grey, ...) are only supported since IE 8.0. IE 3 to IE 6 only support the 'a' variants: gray, ...". Earlier versions of IE need not concern us, because MediaWiki has not supported IE 5 or earlier for some years, and in October this year dropped support for IE 6 also; and for those using IE 7, the existing code uses the "a" spelling, which works all the way back to IE 3. --Redrose64 (talk) 23:18, 4 December 2014 (UTC)

text: Done —  (e • t • c) 16:00, 16 December 2014 (UTC)
thread_title:  Template-protected edit request on 4 December 2014 

message: To fix an issue, which can be demonstrated by just looking at mobile version of Template_talk:Bar_box in FF/Chrome, or just in Android app (see last Barfoobaz orange bar), please replace
    
with
   
—Mykhal (talk) 17:30, 22 October 2017 (UTC)
replies: text: Verified experimentally, in different Wikipedia language incarnation, that such a fix works (this template fix, verified e.g. on this page). —Mykhal (talk) 18:08, 22 October 2017 (UTC)

text: Please describe the problem in more detail. I've looked at the mobile version of Template talk:Bar box in Chrome (on Mac OS X) and see no problem.  The cs.wikipedia.org doesn't seem relevant, since it has something to do with   followed by a regular space, then the &mspace; entity, which isn't under discussion here.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  04:55, 23 October 2017 (UTC)
replies: text:  Below is a better example, which on Chrome for Android shows that Barfoobaz is twice the height of Bazbar. --Ahecht (TALKPAGE) 14:43, 25 October 2017 (UTC)

text: You can see how this looks on Chrome for Android at :File:Ahecht Screenshot Bar Percent.png. --Ahecht (TALKPAGE) 15:44, 25 October 2017 (UTC)

text: Not done for now: I'm not seeing any issue with the mobile version of Template talk:Bar box on Chrome for Android either. I'm closing this edit request until more details are provided. --Ahecht (TALKPAGE) 14:36, 25 October 2017 (UTC)
replies: text:  seems reasonable, so now done. Frietjes (talk) 15:46, 25 October 2017 (UTC)
replies: text: Beat me to it. :-)  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  20:19, 25 October 2017 (UTC)
thread_title:  Edit request 2 

message: I don't see the benefit of specifying min-width: 8em; in the third line of this template. The only thing it seems to accomplish is to generate a lot of useless whitespace in cases where all the labels are quite short. See, e.g., the first example in the {Bar box} documentation. Unless there is some good reason not to, I propose removing it. I have already done that to the similar Template:Bar percent 2 and Template:Bar percent 3, with no ill effects observed in any of the articles where those templates were being used. (Note that before my change to {Bar percent 2}, the third example in the {Bar box} docs required scrolling to see the whole table, and the same problem could be seen in some of the uses of the template in articles. I haven't found any examples of that in articles using this template, but surely they're out there…) - dcljr (talk) 12:15, 12 March 2022 (UTC)
thread_title:  Remove min-width