Template talk:Ambox/Archive 13

Archive 10

Archive 11

Archive 12

Archive 13

The catastrophically broken ambox system

For many years already, articles have been tagged with "issue tags." There are all different types of issue tags. POV, unreferenced, bare URLs, just to name a few. There are dozens of them. New ones are created a lot. In fact anyone can create one, and a consensus is not even needed. I have created some myself. They can also be deleted using the TfD process, and I have watched some long in use get deleted.

Here's the problem: they have gotten so out of hand that in many cases, their presence in an article does not always make sense anymore. Quite a lot of the time, they seem to be sitting there indefinitely, and one cannot figure out why they are there. The editor who originally tagged the article often has disappeared from the project, and the reason why the tag has been placed there to begin with cannot be determined. Not to mention, there are actually quite a lot of tags themselves that have a very ambiguous meaning, and many people do not really know what they are.

Here's another question: who are the tags for? Are they for the readers, the editors, or both? Or are some for the readers and some for the editors? This is yet another thing that remains unclear. The tags have gotten to be so overwhelmingly used that they are to the point of being an eyesore.

I am not in favor of abolishing the system, just revising it so that: 1.) The clear meaning of every tag be known to everyone who views the page, and there be a link to the policy or guideline it references 2.) The reason a tag was placed be stated in the tag, possibly in a collapsible section in case the explanation is long, so editors can more easily figure out how to solve the problem and fix it and know when to remove it 3.) The exact date a tag was placed (not just the month) be within the tag 4.) There be a link to the editor who placed the tag, so that editor can be contacted if possible to be asked more details as to why s/he placed it there 5.) Some tags seem to remain indefinitely and the issues never fixed. There should be a project aimed at getting to those that have remained beyond a certain amount of time.

Sebwite (talk) 19:35, 1 May 2012 (UTC)

After you had finished ranting, there were some interesting points there :)

1. Yes, the meaning of every tag should be clear, and there should be a relevant link to get more information. If you know any templates which don't do this, please fix them or draw my attention to them so that I can fix them.
2. I think in some situations this might be a good idea. For example it is now mandatory to add a reason when using the {{cleanup}} tag. However in other cases, e.g. {{wikify}} I'm not sure what other reason could be given except "this article needs wikifying"!
3. In fact I asked the bot's operator a while ago (see User talk:Anomie/Archives/2012#Questions from MSGJ) whether the date could be added to the template along with the month and year. This would obviously be a prerequisite before this can be displayed on the template. His response can be seen there.
4. Yes, this might be a good idea, and this info could be added by the bot at the same time as the date is added. I might make the suggestion to Anomie.
5. There are various projects (see Wikipedia:WikiProject Council/Directory/Wikipedia#Maintenance) which work on various maintenance issues. But editors will only work on what is of interest to them and there are no deadlines on Wikipedia.

Regards — Martin (MSGJ · talk) 14:03, 17 June 2012 (UTC)

Re your second ob. Martin, about clarification on the Talk page, I think it should be mandatory to put in an entry there even in the "exceptional" case you cite. Doing so provides a ready place for the tag to be discussed and focuses any discussion. It obliges the tagger to think about and cite at least one example, or simply to say the entire article needs deleting or rewriting urgently. It also provides an author who can be referred to contacted etc. LookingGlass (talk) 19:27, 15 December 2012 (UTC)

Small ambox

There is a discussion currently taking place at Template talk:Unreferenced section#Date not showing about the small form of the ambox template and, in particular, whether these templates should be display the tagging date like the full-size amboxes do. Any comments there would be welcome. — Martin (MSGJ · talk) 21:56, 1 June 2012 (UTC)

More structure for this template

I'd like to add some new parameters to this template, which would allow us greater control over the formatting. It will greatly help with proposed changes being discussed here. — Martin (MSGJ · talk) 19:08, 11 June 2012 (UTC)

Talk page link

A lot of amboxes contain a sentence which is similar to "Relevant discussion may be found on the talk page." I propose we add this to ambox which will be called via a talk parameter, which will either be the name of the talk page or the name of the section on the talk page. — Martin (MSGJ · talk) 19:23, 7 June 2012 (UTC)

This is now coded on the sandbox and awaiting comments. The talk parameter can be either

• the name of the section on the talk page of the article
• a link to a different talk page (plus section anchor if needed)

the case will be determined by parser functions automatically. See the examples below. — Martin (MSGJ · talk) 09:28, 8 June 2012 (UTC)

{{ambox/sandbox|text='''There is something wrong with this article.'''|talk=Foo}}

produces

and

{{ambox/sandbox|text='''There is something wrong with this article.'''|talk=Talk:Banana#Foo}}

produces

I have now deployed this code. — Martin (MSGJ · talk) 20:15, 11 June 2012 (UTC)

Would it be a good idea to roll out this feature to all ambox templates? So that |talk=Foo would always give a link to section Foo on the talk page, whichever template you were using. — Martin (MSGJ · talk) 21:44, 30 June 2012 (UTC)

I think it would be a good idea. —SamB (talk) 17:57, 27 July 2012 (UTC)

issue / fix

Most template messages are separated into

• an issue (e.g. This article may need to be wikified to meet Wikipedia's quality standards.) and
• advice for fixing the issues (e.g. Please help by adding relevant internal links, or by improving the article's layout.)

I propose that we add two parameters issue and fix designed for these two sentences. The current parameter text would still be supported for templates which do not fit this model. The advantages would be as follows:

• Being able to display one without the other (the main application for this would be displaying a shortened version on {{multiple issues}})
• Displaying the talk page link (described above) in a more natural position between the issue and the fix.
• Allowing consistent control over formatting, for example making the issue bold.

— Martin (MSGJ · talk) 19:33, 11 June 2012 (UTC)

No comments, so deployed — Martin (MSGJ · talk) 17:16, 22 June 2012 (UTC)

Thanks for doing this. Could you please update the documentation as well? GoingBatty (talk) 00:10, 1 July 2012 (UTC)

Yes, there is going to be a complete overhaul of the documentation in due course, because there are lots of changes that need to be made! — Martin (MSGJ · talk) 07:30, 1 July 2012 (UTC)

I've started work on this. — Martin (MSGJ · talk) 21:41, 5 July 2012 (UTC)

Documentation is finished. Perhaps you could let me know what you think? — Martin (MSGJ · talk) 16:09, 9 July 2012 (UTC)

Very nice! I fixed a few typos and combined the issue and fix sections. Should there be a better example than {{citation style}}, since it doesn't link to a policy or guideline? Thanks! GoingBatty (talk) 23:18, 11 July 2012 (UTC)

• So, |fix= isn't used if the template is used inside of {{multiple issues}}? How then are new editors that are creating their first article learn how to improve and fix them? OR is this a bug where it is not working with the essay, tone, and orphan templates? I'm kind of here. — User:Technical 13   ( C • M • View signature as intended) 13:01, 2 April 2013 (UTC)

It's not a bug. The goal of using {{Multiple issues}} (in both its current and previous incarnations) is to reduce the amount of space taken up on articles with many maintenace templates. The trade-off is removing some of the text that may be helpful to fix the issue, and then ultimately remove the template. GoingBatty (talk) 14:10, 2 April 2013 (UTC)

I think that instructions on possible ways to fix an article are crucial to new editors. That being said, would there be a way to offer an on-hover set of instructions to something that otherwise shows as a small "(FIXES)" or something of the sort? I think that would help the new editors learn how to fix their articles and get the issue templates removed instead of getting frustrated because their article has been deleted. There seems to be a lot of "Why did my page get deleted?" or "How can I keep my page from getting deleted?" type questions on WP:TH and WP:HD type forums. — User:Technical 13   ( C • M • View signature as intended) 14:31, 2 April 2013 (UTC)

Span around text

It is proposed to make this edit to Template:Ambox/core which will allow us to control which part of the message is displayed when using Template talk:Article issues. For further discussion please see Template talk:Multiple issues#Suggestion. — Martin (MSGJ · talk) 16:00, 13 June 2012 (UTC)

This change has now been made. — Martin (MSGJ · talk) 21:37, 14 June 2012 (UTC)

Comment guff

Wrapped around a lot of these templates is HTML comment like

<!--{{Fringe theories}} begin-->

and

<!--{{Fringe theories}} end-->

I imagine this was to aid fixing incorrectly substituted templates, but now we have the proper substitution detection I don't believe there is any need for this and it just makes the code look messy. — Martin (MSGJ · talk) 21:12, 15 June 2012 (UTC)

See this edit that even with the detection we need an indicator of where the template starts and where it ends. Also, I wasn't very pleased to see that you remove this without first seeking consensus. Also, messy is a relative concept. I do not find the addition of those remarks messy, rather they impart a feeling of order, imho. Debresser (talk) 19:39, 16 June 2012 (UTC)

Ah, so you are still here. I think we are the only two editors watching this template and I was wondering if I was on my own here! In response to your points,

even with the detection we need an indicator of where the template starts and where it ends

I would question how much the comment helps here. Most people working with templates would understand that the double braces indicate the start and end of the template call. But in situations like this, using undo is the much easiest solution and doesn't require any knowledge of the code.

I wasn't very pleased to see that you remove this without first seeking consensus

It is a very minor change and this is the first time anyone has questioned this, so I had no idea it would be controversial. Also I could turn this around and ask whether there was any consensus to add this stuff in the first place. (If so, perhaps you could point me towards the discussion.) Anyway I have now stopped removing it and am happy to discuss.

messy is a relative concept

Yes, I suppose it is :) One person's mess is another person's feeling of order I suppose. — Martin (MSGJ · talk) 13:50, 17 June 2012 (UTC)

Yes, I sometimes also think we are alone here. I think this is a wonderful template, and you are doing good things with it. You are, of course right about the fact that a knowledgeable editor will simply press "undo" or will know what code to remove, but we should take into account that not all editors are as knowledgeable and who knows where we will be in another five years etc. So I think the comment has a function and should stay or be (re-) added where it is absent. Debresser (talk) 18:47, 17 June 2012 (UTC)

There are 181 people watching this page, so where are they all? I still disagree with you about the comment, but as I stated above, I am stopped removing it until we get a consensus either way. — Martin (MSGJ · talk) 11:05, 21 June 2012 (UTC)

I dunno about the other 180, but I'm here, I just don't check this page every day.

I'll merely echo debresser's comments: a.) you're doing some good things and b.) I think that in general the "start/end" comments are very helpful. - jc37 20:30, 26 June 2012 (UTC)

Tracking category

In order to track which amboxes have the name parameter set I am planning to set up a tracking category (perhaps Category:Article message templates) to place all named amboxes in. Category:Article message boxes will gradually clear out as the names are added. The advantage of this method is that we will only categorise the actual ambox templates and not every page in the template namespace which transcludes one of them. — Martin (MSGJ · talk) 21:16, 15 June 2012 (UTC)

I've now made this change. — Martin (MSGJ · talk) 08:48, 16 June 2012 (UTC)

The name parameter has now been added to all the amboxes and Category:Article message boxes is now clear. Shall we delete this category and keep using Category:Article message templates, or switch back? — Martin (MSGJ · talk) 11:06, 21 June 2012 (UTC)

I think this should be a CfD question. Personally, I'm torn on the issue, and would like to hear others' thoughts on this. - jc37 20:33, 26 June 2012 (UTC)

You're welcome to take it to CfD but it seems a rather trivial issue, and is "back of house" — Martin (MSGJ · talk) 20:43, 26 June 2012 (UTC)

I understand, but you'd be surprised (well you probably wouldn't) how what may seem minor are suddenly big deals when dealing with category names.

I'll be happy to start a CfD, but I'd ask if you would write the nom/explanation, as I'm fairly certain that you would explain it better than I would : ) - jc37 20:52, 26 June 2012 (UTC)

I'd rather not, simply because I have no opinion one way or the other. I needed to introduce a new tracking category for a technical reason, which I have now finished. Whether we stick with the new one or go back to the old one makes no difference to me ;) — Martin (MSGJ · talk) 13:20, 27 June 2012 (UTC)

I have seen many cases where changes were made to templates reflecting on categories, and unless somebody found a serious problem, these were not dealt with at Cfd. I propose to do the same in this case. Debresser (talk) 14:39, 27 June 2012 (UTC)

Supplementary material

Some templates (e.g. Template:Wikify) have some extra content which appears after the date. There is currently no way to display this properly using the issue, fix and date parameters. I propose to add an extra parameter supp to support these templates. Anything put inside this will be hidden inside the small and compact forms. — Martin (MSGJ · talk) 19:45, 26 June 2012 (UTC)

Are they all "how to" sections? I think "supp" is probably too vague. - jc37 20:35, 26 June 2012 (UTC)

In fact I only know of that one, although it is possibly something which may be used elsewhere. Alternative names would be good, but the only minor consideration is that all the current parameter names have 5 characters or less and keeping within this limit would keep the code aligned nicely :) — Martin (MSGJ · talk) 20:47, 26 June 2012 (UTC)

Other possibilities: ps for postscript, add for addendum or additional, info for additional information. — Martin (MSGJ · talk) 11:36, 27 June 2012 (UTC)

Unless there are further comments in the next day I intend to go with info for this parameter. — Martin (MSGJ · talk) 10:12, 28 June 2012 (UTC)

Article / section

A lot of ambox templates have code to allow the wording to change based on whether it is applied to an article or a section of an article. Some go further and will allow variants such as list, biographical article, section of a biographical article, etc. Currently this is rather haphazard and the method to do this varies from one template to another. On some you must do

{{Wikify|section|date=}}

whereas on others you have to do something like

{{Cleanup-rewrite|section=yes|date=}}

I'd like to bring this code to the meta-template and make it consistent across all templates, so that you do not have to study the documentation of each separate template to learn how to do this. — Martin (MSGJ · talk) 11:41, 27 June 2012 (UTC)

Been racking my brains for a suitable parameter name for this. type is an obvious choice, but it is already used by ambox for something else. So how about form or mode? I think an unnamed parameter would be easiest to use for ambox templates, so we could choose to keep it unnamed at the meta-template as well. — Martin (MSGJ · talk) 10:50, 29 June 2012 (UTC)

'Unnamed' you mean like {{Wikify|section}}? That seems to me to be by far the most common way. I think this is a very good proposal. Debresser (talk) 20:08, 30 June 2012 (UTC)

Yes, we will keep it as an unnamed parameter on the templates that use ambox, but I think it would be sensible to give it a name on the meta-template. What about sect for section? So we would pass it through to ambox by specifiying |sect={{{1}}} on each template. — Martin (MSGJ · talk) 21:20, 30 June 2012 (UTC)

I have now added this functionality, along with some code efficiencies. — Martin (MSGJ · talk) 05:54, 5 July 2012 (UTC)

Default to small for section templates

What do people think about defaulting to the |small=left format for section templates? In other words, if someone types {{Unreliable sources|section}} it will automatically display the small format

instead of the standard format

Some templates already do this actually. There would still be the option for an editor to override the default by specifying |small=no. — Martin (MSGJ · talk) 16:19, 9 July 2012 (UTC)

• Note: there was some discussion on section templates at the village pump, although no consensus developed. Consistency was important for some of the participants of that discussion, and this proposal might help with that. — Martin (MSGJ · talk) 16:27, 9 July 2012 (UTC)

I have seen this style more and more lately. I personally like the large template better, but - as always - favor a uniform style. Debresser (talk) 22:28, 9 July 2012 (UTC)

Yes it looks terrible if adjacent templates are using different formats! I'm thinking we could maybe adjust the small format to be a little less narrow. There were some other suggestions on that discussion I linked to as well, such as making the text flow around the box. — Martin (MSGJ · talk) 22:43, 9 July 2012 (UTC)

Note: I have informed the four participants of the previous discussion, in case they are interested in this. — Martin (MSGJ · talk) 08:17, 11 July 2012 (UTC)

There are a few minor issues with the small format, one is that the left makes the appearance unbalanced, another is that the tag takes more vertical space, which is at a premium near the top of a page. Rich Farmbrough, 20:31, 11 July 2012 (UTC).

This is rather interesting, and difficult to handle. Certainly space is a premium in many articles, and in others it's not the topmost priority. Uniformity is great, and it really can cause problems in some places too. Leaving it up to the editor works well to tailor the solution and get the best results from one wikiproject to the next with the different lengths and types of articles, but when it comes to uniformity, it's not breaking ranks to create a new default, it's simply creating a new norm. Then there is the whole alarm that some people seem to suffer from any changes, like the watchlist. Introduced, massive alarm, withdrawn, massive withdrawal symptoms, and eventually maybe they find the balance. This is nowhere near as big as the watchlist thing, but there'll still be some outcry, with luck, maybe one or two "ARRGHH I AM GOING TO DIE, IT'S THE END, 43:12 some bible verse" yeah, there has to be at least 3 of them for any good idea, and 3 dozen for any new thing project wide. There is the semi sneak-attack as well, having the cybernetic editors use them as default when they are tagging articles, but getting good comments for good ideas is harder, people are less likely to say 'this is fantastic' when they like it then they are to say it sucks if they don't like it. I guess asking more people and hassling them for an opinion is a good idea, but I am not suggesting it's any reason to stop, it's not, just thinking if you can catch the editors who are adding the tags into articles and survey them a little, you may get a lovely little CONSIDERED consensus, rather that the creme of the crap hit and run 'idontlikeanythingatallexcepttellingyouidon'tlikeit' sort of comments that go nowhere (ask them why is like asking why does the parrot want a cracker).

In short this is a good idea, and should be trialled a bit wider, and I love the sound of my own voice. Penyulap ☏ 00:38, 12 Jul 2012 (UTC)

can the text wrap around as default too ? Penyulap ☏ 00:39, 12 Jul 2012 (UTC)

My biggest problem with this proposal (as I stated in an earlier discussion about this issue) is that the date of the tag is not present. That, up until now (recently?), was always there. For me, when editing an article with this tag, I can then see at a glance how long the lack of sourcing has been tagged to decide whether I should remove unsourced material.--Bbb23 (talk) 00:16, 13 July 2012 (UTC)

Agreed. A date should be there. Debresser (talk) 00:36, 13 July 2012 (UTC)

Multi-fix edit

Some specific subjects listed at Wikipedia:Template messages/Cleanup#Cleanup of specific subjects have one issue but different fixes for that same issue. For example, for the issue "This astrology-related article may require cleanup to meet Wikipedia's content standards," there are different fixes that are often needed in astrology-related articles. Is it possible to edit the template to provide multiple fix options, e.g. fix1=, fix2=, fix3=, ... fix5=, etc. so that users of specific subject clean-up templates can specify one or more pre-phrased fixes by, for example, specifying {{Cleanup-astrology|section|fix2=yes|fix5=yes}}? See current discussion at Template talk:Cleanup-astrology. -- Uzma Gamal (talk) 19:23, 21 October 2012 (UTC)

Wikipedia:Manual of Style/Article message boxes

Wikipedia:Manual of Style/Article message boxes should be tagged as historical. It's not really a style guideline; it appears to have been an attempt to standardise the design of message boxes, in an era where message boxes were wildly inconsistent. These days, they all use {{ambox}}, so there's simply no need for this guideline any more.

(I realise this is an odd place to be having this discussion, but for some reason the guideline's talk page redirects here. So here we are...) DoctorKubla (talk) 09:44, 28 November 2012 (UTC)

I agree and it is not the first time this has been suggested. So I have made the change. — Martin (MSGJ · talk) 10:47, 28 November 2012 (UTC)

Oh, okay. That was nice and straightforward. DoctorKubla (talk) 13:52, 28 November 2012 (UTC)

Using this on another wiki

I'm trying to use this on another MediaWiki wiki, hosted by Wikia, but it doesn't seem to work. I have pasted in the CSS and got the core and ambox templates, yet the box and colors won't appear. Can someone give me advice on everything I need to use this template? Thanks in advance Xtreme2000 (talk) 21:01, 8 December 2012 (UTC)

Ignore me, I've manage to get it to work :P Xtreme2000 (talk) 10:18, 9 December 2012 (UTC)

What was your fix? ~ Michael Chidester (talk) 03:26, 24 December 2012 (UTC)

Having all maintenance template reasons display within multiple issues

Several maintenance templates contain a |reason= parameter to allow additional information to be displayed, in order to help editors understand what needs to be fixed. When we wrap these maintenance templates within {{multiple issues}}, some templates still display the |reason= parameter (e.g. {{cleanup}}), while others do not (e.g. {{BLP sources}}). When I requested for an update to {{BLP sources}} to make it more like {{cleanup}}, it was suggested I come here instead for assistance in updating {{ambox/core}}. What do others think? Thanks! GoingBatty (talk) 00:32, 3 March 2013 (UTC)

I think the reason is that some templates use {{mbox}} rather than {{ambox}} and the former has not kept up with all the updates that this template has had. I'm not sure what the solution is, but I did make a comment last year about this. — Martin (MSGJ · talk) 11:23, 3 March 2013 (UTC)

Actually perhaps this is not the issue in this case. In {{BLP sources}}, the reason is passed via the info parameter which was briefly discussed above (but not yet documented apparently). Are you proposing that a reason parameter be incorporated into {{ambox}}. How many maintenance templates actually use a reason parameter? — Martin (MSGJ · talk) 11:28, 3 March 2013 (UTC)

Looking at each of the templates in Category:Article message templates, I see that the reason is part of the |issue= parameter in nine templates: {{cleanup}}, {{cleanup-school}}, {{cleanup-university}}, {{confusing}}, {{expand article}}, {{expert-maths}}, {{lead rewrite}}, {{medref}}, and {{music-examples}}. {{BLP sources}} seems to be the only one with the reason in the |info= parameter, and {{repair coord}} has the reason in the |text= parameter.

The only technical solution I was proposing was to change {{BLP sources}} so that the reason is part of the |issue= parameter. However, I'm open to other suggestions. Thanks! GoingBatty (talk) 02:50, 4 March 2013 (UTC)

I have made the change to {{BLP sources}}, but I think it may be worth adding support for the reason parameter to this template. — Martin (MSGJ · talk) 08:45, 5 March 2013 (UTC)

Thank you for updating {{BLP sources}}. I'll keep this page on my watchlist to continue participating in this discussion. GoingBatty (talk) 20:13, 5 March 2013 (UTC)

template:ambox

could someone add these codes to the section with the support for templates

{{Category handler
 |nocat={{{nocat|<noinclude>true</noinclude>}}}
 |main={{Ambox/category
  |cat={{{cat|{{{category|}}}}}} 
  |all={{{all|}}}
  |date={{{date|}}}
 }}{{Ambox/category
  |cat={{{cat2|{{{category2|}}}}}} 
  |all={{{all2|}}}
  |date={{{date|}}}
 }}{{Ambox/category
  |cat={{{cat3|{{{category3|}}}}}} 
  |all={{{all3|}}}
  |date={{{date|}}}
 }}

Paladox2014 (talk) 18:07, 28 April 2013 (UTC)

I'm personally not sure what you are asking for, it appears that the code you've specified is already in the template. Either way, you'll need an admin to apply your change since it is a fully protected template. Let me summon one for you...

Paladox2014 want some code added to or moved around in this template. I can't figure out what he wants, as you can see from my comment. I'll leave it to whichever admin answers this to figure out what they are looking to get added to or moved around in the template. Have a nice day! Technical 13 (talk) 18:17, 28 April 2013 (UTC)

That code is already there, so there is nothing to edit. Paladox, you need to provide more information about what your edits are supposed to accomplish. — Edokter (talk) — 18:35, 28 April 2013 (UTC)

what I mean is I know they are there but they are for the article section not for the template section 109.155.55.77 (talk) 19:32, 28 April 2013 (UTC)

You mean the documentation section? You can freely edit the documentation page. — Edokter (talk) — 19:41, 28 April 2013 (UTC)

In the phrase above "they are for the article section not for the template section", if we substitute the word "namespace" for "section", it reads to me as a request for the correct {{ambox}} equivalent for use in template namespace. That would be {{tmbox}}. I note that a template {{Expand template}} has recently created by Paladox2014 (talk · contribs) which is constructed around {{ambox}} - but (leaving its intended purpose aside) I suspect that it should use {{tmbox}}. --Redrose64 (talk) 20:21, 28 April 2013 (UTC)

Edit request on 5 May 2013

Please change the content Template:Ambox/core to the content reflected in the appropriate sandbox. This edit replaces superseded raster images with vectorized equivalents. The files have been protected on Commons and the cascading protection option will also apply. I don't think I need to explain reasons why scaleable vector graphics are more advantageous than raster images. Thank you for your support. --Addihockey10 ^e-mail 06:44, 5 May 2013 (UTC)

It doesn't just replace the images, it completely changes the code. Can you describe the code changes as well? In case you only want to replace the images, you need to create a version that reflect the current code. Thank you Petrb (talk) 06:53, 5 May 2013 (UTC)

 Done Petrb (talk) 07:02, 5 May 2013 (UTC)

 Undone. The PNGs were specifically crafted to produce sharper images then the rendered SVGs. Plus not all images on Commons are protected, and cascaded protection does not work on images hosted on commons. — Edokter (talk) — 11:43, 5 May 2013 (UTC)

Ok, sorry for problems if it caused some, however, I disagree that png can be technically sharper than vector graphics. Vector will be always more sharp or same sharp, no matter of resolution. Petrb (talk) 18:45, 5 May 2013 (UTC)

Additionally, I talked to Brion on IRC today and he said that one of the thing's he will be pushing for is for small size .svgs will render naturally as .svgs. I can't remember all the details, but for unreasonably sized SVGS (where the svg is much bigger than the rendered png) or buggy SVGS it will automatically default to PNG. In this case I don't see what's wrong with replacing the outdated raster images with the SVGs. Thanks. --Addihockey10 ^e-mail 03:39, 6 May 2013 (UTC)

Should this template be made smaller?

I don't think it needs to be this big. A couple hatnotes, an infobox, a sidebar, maybe an image, the ToC, a couple of these and a short lead, and you have to scroll twice the length of your screen for content. We should do what we can to emphasise content. — Lfdder (talk) 22:39, 12 September 2013 (UTC)

There is plenty in the archives of this page about size. As thinks stand, it's consistent with many other templates. --Redrose64 (talk) 23:20, 12 September 2013 (UTC)

And consistency is more important? Amboxes are very rarely used alongside other *boxes anyway. — Lfdder (talk) 16:20, 14 September 2013 (UTC)

Any example articles, that you're thinking of in particular?

Note that there is already a |small=left option in some (all? most?) of the templates that use ambox.

And if there are more than a couple of amboxes on a page, they can usually be compressed into a {{multiple issues}} box. –Quiddity (talk) 19:03, 14 September 2013 (UTC)

By no means the worst: [1] — Lfdder (talk) 19:14, 14 September 2013 (UTC)

Tabs on top, that sidebar on the left you can't hide, two of these and the infobox, and that's all the content that fits on the screen. — Lfdder (talk) 19:17, 14 September 2013 (UTC)

In fairness, the lead section is generally all that fits on a screen (especially at 1024x768), regardless of the presence of amboxes or an infobox. See any recently Featured Article, for examples, Eg. Middle Ages and The Hunger Games were TFA on the Main Page recently.

We can hide the lefthand sidebar through User:PleaseStand/Hide Vector sidebar but it is quirky.

You might be able to get more vertical space by right-click customizing the layout of your browser-toolbars (if you haven't already), eg my Firefox is setup like this [2]. HTH. –Quiddity (talk) 20:11, 14 September 2013 (UTC)

I use Chrome (can only show/hide the bookmarks bar), but thanks for the suggestion. — Lfdder (talk) 20:59, 14 September 2013 (UTC)

Here's a gem: Armenians in Cyprus — Lfdder (talk) 02:01, 21 September 2013 (UTC)

Switch of mbox templates and category handler to Lua

I've made a request over at Template talk:Mbox about switching all of the {{mbox}} family templates, plus the {{category handler}} template, to use Lua modules. These templates have millions of transclusions, so I would appreciate comments and some more eyes on the code. Please let me know what you think over at the request page. — Mr. Stradivarius ^{♪ talk ♪} 15:09, 15 October 2013 (UTC)

The proposed changes are now up live - this template has been switched to use Module:Message box. — Mr. Stradivarius ^{♪ talk ♪} 12:59, 20 October 2013 (UTC)

Question

I have seen | subst = <includeonly>{{subst:</includeonly><includeonly>substcheck}}</includeonly> being replaced by | subst = <includeonly>{{subst:substcheck}}</includeonly> often. Is that okay, and if that is okay, shouldn't we update the documentation? Debresser (talk) 20:14, 19 October 2013 (UTC)

Good idea, and I've added it. By the way, the reason you might have seen it being used a lot is that was the code used in the "common parameters" box. Presumably editors were just copying the code wholesale. — Mr. Stradivarius ^{♪ talk ♪} 13:03, 20 October 2013 (UTC)

Most likely. Most editors copy the code of templates from the documentation. Debresser (talk) 16:17, 4 January 2014 (UTC)

Categories

I have added a warning to the documentation regarding the "cat" and "all" parameters that they should not be linked, nor should "Category:" be used. What ever happened to the "cat-date" parameter? Debresser (talk) 16:17, 4 January 2014 (UTC)

Testcase "talk= name=foo page=template:foo text=text" and the one directly below it.

Mr. Stradivarius, I don't know if this is related to the change that was just made to the module or something that has been there for awhile. In Template:Ambox/testcases#talk= name=foo page=template:foo text=text the link to the "talk page" is set to go to section #.23 which is ## decoded... Is that intentional? Technical 13 (talk) 01:22, 27 January 2014 (UTC)

That was like that before, and is actually a feature of MediaWiki, not of the module - see my sandbox for a demonstration. A little more complex is the question of why the ambox template put a hash in the fragment by default. I am assuming that the previous template needed a non-blank value, and the hash sign was a convenient one to use because it is unlikely to be a section heading, but I could be wrong there. — Mr. Stradivarius ^{♪ talk ♪} 02:01, 27 January 2014 (UTC)

Protected edit request on 20 March 2014

213.55.73.118 (talk) 21:57, 20 March 2014 (UTC)

Not done: it's not clear what changes you want made. Please mention the specific changes in a "change X to Y" format. — {{U|Technical 13}} ^{(t • e • c)} 22:01, 20 March 2014 (UTC)

Feature request

Is it possible that this template produces "The article ..." instead of "This article ..." when used inside the {{multiple issues}} template? (This would require the sect parameter to be used of course.) This would improve the wording when multiple issues are used. — Martin (MSGJ · talk) 10:39, 10 June 2014 (UTC)

@Mr. Stradivarius:, could you advise on this? Thanks — Martin (MSGJ · talk) 13:11, 20 June 2014 (UTC)

Text is not set here. You should ask this at Template talk:Multiple issues. -- [[User:Edokter]] {{talk}} 17:13, 20 June 2014 (UTC)

The text I am talking about is set here (or rather Module:Message box). — Martin (MSGJ · talk) 19:59, 20 June 2014 (UTC)

In that case... Module talk:Message box. :) -- [[User:Edokter]] {{talk}} 22:06, 20 June 2014 (UTC)

We could do this, but we'd have to add a parameter so that we could set it in {{multiple issues}}. Any preferences on parameter naming/format? — Mr. Stradivarius ^{♪ talk ♪} 01:14, 21 June 2014 (UTC)

That doesn't sound right. Multiple issues does not actually call this template - it just sets up the class="hide-when-compact" which then means that some of the text is not displayed inside it. I'm not sure if we can use class="show-when-compact" which could then be used to display "The" instead of "This". It's a minor issue, so not worth coding anything complicated. Regards — Martin (MSGJ · talk) 13:45, 23 June 2014 (UTC)

Edokter, the message box module powers lots of different message boxes, and this issue is only related to article messages boxes, so I still maintain this is the correct venue :) — Martin (MSGJ · talk) 13:45, 23 June 2014 (UTC)

Change the color of the "Deletion" tag (not to be confused with the "Speedy Deletion" tag)

Excuse me, but would it be possible if we could change the color of the "Deletion" tag (maroon) to at least something close to a broad shade of red (a color which does not seem brighter than the used-for-content-messages orange)? I know that we can disambiguate those two tags because the speedy deletion one has a pale red color for its background, but, because they are both maroon on their left, that can confuse us from knowing whether one tag is for speedy deletion or just deletion. This idea of me is just to prevent ambiguity. Gamingforfun³⁶⁵ (talk) 06:37, 19 August 2015 (UTC)

What benefit do you see from distinguishing between the two? And how does that advantage outweigh the increased complexity of a more varied colour scheme? —Psychonaut (talk) 07:43, 20 August 2015 (UTC)

Please don't use the edit protected template for feature requests. Only use it to request uncontroversial changes. -- [[User:Edokter]] {{talk}} 10:54, 20 August 2015 (UTC)

Amboxes are not shown in mobile version

In contrast to omboxes, amboxes are not show in the mobile version. The boxes are completely omitted or produce error messages like "There are problems with this page". In the mobile version you can see the source code of these boxes but they are not presented. Do you know why? --RolandUnger (talk) 18:25, 8 November 2014 (UTC)

You can show them by clicking "there are problems with this page". This is done to conserve visual real estate. (some articles otherwise won't start for 2 pages). —TheDJ (talk • contribs) 19:25, 4 March 2015 (UTC)

@TheDJ: Is there any way to override this behavior? On Lunar eclipse there is a helpful box at the top that shows the date of the next eclipse, but this just shows up as "This page has some issues" on the mobile version. 28bytes (talk) 11:53, 25 March 2015 (UTC)

@28bytes: No, there is no way to override this. —TheDJ (talk • contribs) 12:21, 25 March 2015 (UTC)

Do you know if there is a better template to use for this purpose? 28bytes (talk) 12:34, 25 March 2015 (UTC)

Report this as a bug with the mobile site. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:32, 25 March 2015 (UTC)

Thank you Andy, I will do that. 28bytes (talk) 15:47, 25 March 2015 (UTC)

 Done: T93922. 28bytes (talk) 18:08, 25 March 2015 (UTC)

Any content should never be placed in an ambox. Information such as the next eclipse is better served in an infobox (if there is one), or a hatnote (but these are sometimes hidden as well). -- [[User:Edokter]] {{talk}} 19:00, 25 March 2015 (UTC)

I think the default behavior should be overridden for amboxes that allege factual error or say that this article contradicts another article. Also, what of amboxes that appear other than at the very top? If an ambox appears in a section, for example, then the “This article may have issues” notice should appear there, instead of being suppressed. 96.255.148.25 (talk) 18:18, 13 July 2015 (UTC) (UTC)

Is this problem already unsolved? I see it is causing problems in the Ambox page itself:

M. Quijada 13:25, 2 September 2015 (UTC) — Preceding unsigned comment added by Manuel.quijada.serrano (talk • contribs)

@Manuel.quijada.serrano: no, it is part of a more general issue. Any templates that use the following classes are hidden by MobileFrontend: ambox, navbox, vertical-navbox, topicon, metadata, nomobile. See Wikipedia:Village pump (technical)/Archive 138#Navboxes in mobile, phab:T55437 and phab:T68747. --Redrose64 (talk) 14:33, 2 September 2015 (UTC)

Discussion that may affect this template

Please see Wikipedia:Village pump (proposals)#Implementing Help:Maintenance template removal. A new parameter may be needed in this template to implement it.--Fuhghettaboutit (talk) 12:42, 14 April 2016 (UTC)

Template-protected edit request on 13 August 2017

Please add borders to the small ambox. Without borders, these amboxes blend into the article. jd22292 (Jalen D. Folf) (talk) 00:35, 13 August 2017 (UTC)

Not done: Styles are controlled at MediaWiki:Common.css. — JJMC89 (T·C) 00:48, 13 August 2017 (UTC)

Solving the mobile issue

The mobile issue could be solved by renaming the CSS classes to something other than "ambox" (either something serious like "cleanupbox" or an internal joke like "drivebytag"). KMF (talk) 01:02, 22 November 2017 (UTC)

Fixing issues on mobile

Hey there! I'm working with my team to improve how issues display in mobile. We understand the current experience is terribly broken and we're keen to fix it. One thing we've noted that would allow us to present issues better is if we were able to reliably access the date. Could the date and brackets be wrapped in a span with class `date`? Jdlrobson (talk) 21:04, 2 March 2018 (UTC)

@Jdlrobson: You didn't link to the initial discussion, Template talk:More citations needed#Semantically mark up date. Please also note that the grave accent character cannot be used as a substitute for a quote mark. --Redrose64 🌹 (talk) 22:54, 2 March 2018 (UTC)

The backticks were probably confusion with the Markdown syntax used in Phabricator, where they have the effect of <code> tags. Much like how '' and ''' in wikitext work as <i> and <b>. Anomie⚔ 12:52, 13 March 2018 (UTC)

Seems perfectly reasonable to me. We could even consider <time> perhaps ? —TheDJ (talk • contribs) 13:33, 13 March 2018 (UTC)

We now have three parallel discussions, see Module talk:Message box#Mark up date so that is is machine readable. --Redrose64 🌹 (talk) 23:05, 13 March 2018 (UTC)

Proposal to change icon set

There's a proposal to change many of the icons used across Wikipedia, including several used with this template. --Yair rand (talk) 23:26, 3 June 2018 (UTC)

Feedback wanted on improvements to Ambox templates on mobile web

Hey all,

The Readers web team is working on improving how article message templates appear on the mobile web. We are focusing on templates that use this template. Right now these templates appear when you tap the gray link under the article title, making it difficult for readers and editors to know whether there are any important issues with the article they are reading. We're trying to make these message templates more visible by displaying their description on the top of the article. We hope this will increase awareness of these issues for readers and editors alike.

We would like to encourage template editors to add the type and issue parameters to your templates (if they're not already there). The type parameter will allow us to visually distinguish the severity of the issue and use the icon associated with that particular template type. The issue parameter will allow us to display only the summary of the issue on the main page. You may then tap on the issue to see details. This will prevent the issues from taking up too much space on the page and distracting from the rest of the content.

We have a project page describing what will be improved. If you have feedback on these changes we'd like to hear from you on the talk page.

Thank you!

CKoerner (WMF) (talk) 09:18, 19 July 2018 (UTC)

Documentation improvement: sub-templates are not used anymore

The section #Technical notes states This template calls {{Ambox/core}} or {{ambox/small}} which holds most of the code for {{Ambox}}, while {{Ambox}} itself does parameter preprocessing. → I suppose this is obsolete, the subtemplates /core and /small are unused since the switch to Lua [3]. — Preceding unsigned comment added by Escalatr (talk • contribs) 06:42, 10 September 2015 (UTC)

Change coming to how certain templates will appear on the mobile web

Change coming to how certain templates will appear on the mobile web

Please help translate to other languages.

Example of improvements

Hello,

In a few weeks the Readers web team will be changing how some templates look on the mobile web site. We will make these templates more noticeable when viewing the article. We ask for your help in updating any templates that don't look correct.

What kind of templates? Specifically templates that notify readers and contributors about issues with the content of an article – the text and information in the article. Examples like Template:Unreferenced or Template:More citations needed. Right now these notifications are hidden behind a link under the title of an article. We will format templates like these (mostly those that use Template:Ambox or message box templates in general) to show a short summary under the page title. You can tap on the "Learn more" link to get more information.

For template editors we have some recommendations on how to make templates that are mobile-friendly and also further documentation on our work so far.

If you have questions about formatting templates for mobile, please leave a note on the project talk page or file a task in Phabricator and we will help you.

Thank you!

CKoerner (WMF) (talk) 19:41, 13 November 2018 (UTC)

12/16/18: When and how or how and when

Moved to Module talk:Message box

18:32, 17 January 2019 (UTC)

RfC of potential interest

An RfC is underway that interested "watchers of this page" wound enhance by participating, I hope that many will! The discussion is located at Wikipedia talk:Twinkle#RfC regarding "Ambox generated" maintenance tags that recommend the inclusion of additional sources. Thank you.--John Cline (talk) 06:38, 29 January 2019 (UTC)

Talk location

As you can see here, the sentence "Relevant discussion may be found on the talk page." is by default placed between the "issue" and "fix" parameters. Is that something new? Doesn't it make more sense to put it after the "fix" parameter?

I previously posted about this at Module_talk:Message_box#Talk_location, but since there were no reactions there, I decided to post here, which probably is the better place anyway for this discussion. Debresser (talk) 12:56, 16 December 2020 (UTC)

Also, would it be possible to have 2 choices to place the talk page sentence? (one to be in the middle, and one to be after issue and fix.) Funandtrvl (talk) 19:54, 16 December 2020 (UTC)

Date and removal notice are too small (per MOS:SMALLFONT) in the small version of ambox

See the test case at issue small. The date and the removal notice are rendered at 74.8% of normal, which is an accessibility problem, per MOS:SMALLFONT. As far as I can tell, a small tag (85%) is being applied to the text as well as some sort of CSS class that reduces the size to 88%. (88%*85%=74.8%)

I think that the small tag can stay, as it is applied to the date and removal notice in the full version of the ambox, and it looks reasonable. The further reduction of 88% applied via a class (I presume), when the small-box version is rendered, needs to be removed. Is there someone more familiar with classes and Lua who can puzzle this out? Thanks in advance. – Jonesey95 (talk) 01:24, 9 May 2021 (UTC)

These are the applicable rules:

html body.mediawiki .mbox-small-left {
  border-collapse: collapse;
  font-size: 88%;
  line-height: 1.25em;
}
small {
  font-size: 85%;
}

I don't know where they're held. --Redrose64 🌹 (talk) 06:44, 9 May 2021 (UTC)

Thanks, that was helpful. It looks like that class lives in MediaWiki:Common.css and applies to multiple "box" templates. It looks like Template:Ambox/styles.css tries to set the font-size to 100%, but I think that ends up being 100% of 75%. I wonder if TheDJ or Ladsgroup, who worked on the latter css file, has any bright ideas. It is not clear to me where the problem should be fixed. One option is to include some Lua code in the Ambox module that says "if small=left, don't shrink the date or the removal notice", but that's beyond my skills. – Jonesey95 (talk) 13:52, 9 May 2021 (UTC)

The TemplateStyles version is unused (see what links here), I presume under the pretense that we have not fully migrated non-metatemplate uses, either to metatemplates or away from the class names. (See also MediaWiki talk:Common.css/to do for related; I haven't scoped the message box stuff there yet.) Accordingly, only the CSS from Common.css loads.

small's setting in Common.css is because browsers are somewhat inconsistent in how large the element is rendered and sometimes less than our minimum, so we set it to the general consensus minimum. (We should consider whether that minimum is still reasonable given that newer skins Minerva, new Vector, Timeless tend toward larger font size, whereas 85% was decided in the days of Monobook.)

Wherever in this module or template is set, I'd probably recommend inline font-size increase of the small text if it is desired to increase the size. It will be something for TemplateStyles at a later date. (Or we can just add it to Common.css now if the small is generally used in ambox.) Izno (talk) 06:41, 3 June 2021 (UTC)

I have implemented a proposed fix at Module:Message box/sandbox and checked it against the test cases. I have submitted an edit request. – Jonesey95 (talk) 14:50, 3 June 2021 (UTC)

"Ambox" listed at Redirects for discussion

A discussion is taking place to address the redirect Ambox. The discussion will occur at Wikipedia:Redirects for discussion/Log/2021 June 19#Ambox until a consensus is reached, and readers of this page are welcome to contribute to the discussion. dudhhr_Contribs 23:39, 19 June 2021 (UTC)

Limited height on mobile

When displaying on mobile this template has a fixed (or maximum) height of two lines of text and overflow is hidden. Unless there's a good reason not to, could someone please remove the height restriction? Thank you in advance. nagualdesign 17:56, 23 June 2021 (UTC)

Mobile display of ambox today is basically controlled by WMF. This will not be happening here. Izno (talk) 19:09, 23 June 2021 (UTC)

(Whom may have some design discussion floating around if you prefer to review there.) Izno (talk) 19:09, 23 June 2021 (UTC)

Fair enough. Thanks for the reply. nagualdesign 19:54, 23 June 2021 (UTC)

MW:Reading/Web/Projects/Mobile Page Issues probably best describes what they have been specifically doing with ambox. MW:Reading/Mobile Friendly Content probably best describes what they are trying to accomplish overall: basically, the MediaWiki software was not initially designed with responsive web design by default, and many existing templates are only optimised for desktop browsers, so they still want to find ways make it more mobile friendly. Zzyzx11 (talk) 01:46, 24 June 2021 (UTC)

Why is ambox the only message box which the "small" parameter works with?

Hello,

As demonstrated by the above, I have to use an ambox outside of mainspace to have a small message box. Does anyone know why this is the case? Looking at Module:Message box, I can't see any reason why it wouldn't work. Does anyone know? Regards, DesertPipeline (talk) 13:45, 25 June 2021 (UTC)

Only the templates with allowSmall = true in the configuration page, per the documentation. Izno (talk) 16:37, 25 June 2021 (UTC)

User:Izno: When you say "configuration page", what are you referring to? Regards, DesertPipeline (talk) 02:45, 26 June 2021 (UTC)

Ah, I found what you mean. I was a bit confused: They do allow small, but not small=left. Would it be okay to change the other message box templates (or perhaps at least ombox) so that they can also use small=left? Is there some reason why this isn't the case already? Thanks, DesertPipeline (talk) 02:55, 26 June 2021 (UTC)

I have a hard time seeing why you would need to do that for the other kinds of boxes. What is the use case? Izno (talk) 05:04, 26 June 2021 (UTC)

User:Izno: See the box at the top of this section. I'd like to be able to use a message box which doesn't have the coloured part on the left, while still making it appear smaller and on the left so it's not too "glaring". DesertPipeline (talk) 06:06, 26 June 2021 (UTC)

No, I don't want to see what kind of box you want, I want to know where and why you want to use it. Izno (talk) 06:11, 26 June 2021 (UTC)

User:Izno: I just want to be able to use small message boxes left-aligned on other Wikipedia pages which aren't articles without having to use an ambox template, causing the coloured part on the left. DesertPipeline (talk) 10:25, 26 June 2021 (UTC)

@DesertPipeline: A long time ago there was a wide variety of message boxes that used different styles, so that the top of a page could look very messy (see c:File:NewbieTags.png). Then in 2007 came message box standardisation (see c:File:NewbieTagsAfter.png), and so we now have the {{ambox}} ones for articles, the {{tmbox}} ones for talk pages, and so on; and it's all neat and consistent. Why would you want to undo that careful work? --Redrose64 🌹 (talk) 10:19, 26 June 2021 (UTC)

User:Redrose64: I don't want to undo any careful work; I simply want to have a small left-aligned ombox for use on pages which aren't articles. DesertPipeline (talk) 10:25, 26 June 2021 (UTC)

You continue to be vague about where you're doing this, with phrases like "outside of mainspace" and "other Wikipedia pages which aren't articles". We can't give proper assistance unless you give us specifics. But, don't try to misuse {{ambox}} (which, as shown in its doc, is for messageboxes on article pages) for a purpose that it wasn't designed for. First, choose the appropriate message box for the namespace concerned, they're listed at Template:Ambox#Mbox family. Then, if it doesn't do what is intended and a change can be justified, propose an amendment on the talk page of that template. So, to suggest a change to {{ombox}}, you would do this at Template talk:Ombox. --Redrose64 🌹 (talk) 18:45, 26 June 2021 (UTC)

User:Redrose64: Sorry. I'd just like, after line 201 in Module:Message box/configuration, the lines

smallParam                  = 'left',
smallClass                  = 'mbox-small-left',

to be added. I should probably put this request there. DesertPipeline (talk) 02:21, 27 June 2021 (UTC)

OK, so you've raised Module talk:Message box#Fully-protected edit request on 27 June 2021. But you still haven't explained where it is that you need to use a small message box, nor why it needs to be small and not the normal size. --Redrose64 🌹 (talk) 08:37, 27 June 2021 (UTC)

fix displays in small version

We have this bit of documentation in Template:Ambox#issue and fix: But when used inside {{Multiple issues}} or with small=left it displays only the issue:, yet with small = left, we see both the issue and the suggested fix. I am not sure which is supposed to be correct, the doc or the template. Izno (talk) 06:03, 3 June 2021 (UTC)

I can't remember what the intention was now ... which do you think works best? — Martin (MSGJ · talk) 11:19, 15 July 2021 (UTC)

Learn how and when to remove this template message

This message is quite ugly and the link takes you to a generic page Help:Maintenance template removal rather than any specific advice to fix the actual issue. I question how useful this actually is. For a start I'd like to explore making the link less intrusive, perhaps a question mark icon with a tool-tip which will link to that page. It would be more useful if each maintenance template had its own help page which describes the issue in more detail and explains how to fix it. — Martin (MSGJ · talk) 11:47, 15 July 2021 (UTC)

User:MSGJ: I've done a small test and it seems the {{tooltip}} template can't be used with an image – the tooltip remains as the link (which in this case is Help:Template removal). Is there any other way to accomplish it? DesertPipeline (talk)

@DesertPipeline: From the documentation for {{tooltip}}:

Accessibility and HTML validity concerns

This template is intended only for use with abbreviations (including acronyms and initialisms).

The Web Content Accessibility Guidelines contain guidelines for using the <abbr> element generated by this template; see section H28: Providing definitions for abbreviations by using the abbr and acronym elements.

Furthermore, the HTML specifications (both those of the W3C and WHATWG) strictly define the <abbr> element as reserved for markup of abbreviations. Abusing it for mouse-over tooltips breaks our semantic markup and makes our content invalid HTML (technically, "not well-formed"; it will pass an basic automated validator test because such a tool can't tell that the logical application of the data to the structure isn't correct, only that tags are nested properly, etc.).

{{tooltip}} is Not For™ the kinds of things you're proposing. Wikipedia doesn't have anything that is for that, really, by design. "Tooltips" are an accessibility nightmare, and any sort of "hidden text" (that only reveals itself when action is taken by the reader) is typically discouraged in the article space — collapsibility of navboxes and etc. being the exception. Keeping the article layout "clean" will always be secondary to making information accessible to all readers.

MSGJ's suggestion about linking to an informational page is the only form this could realistically take. (Though personally I'm not sure I'm crazy about mystery "ⓘ" links dotting the article space, either, no matter what they do.) -- FeRDNYC (talk) 08:25, 6 September 2021 (UTC)

Tooltips - whether produced by (mis)use of <abbr>...</abbr> or otherwise - are generated by the browser. Depending upon the browser, the content of the tooltip may be obtained from either a title="..." attribute or an alt="..." attribute. Since these are attributes of tags, it follows that they cannot themselves contain any markup. So, there is no way for tooltips to contain images. I'm sure I have explained this before. --Redrose64 🌹 (talk) 21:40, 6 September 2021 (UTC)

Draft articles not in category?

Why do drafts tagged with {{Cleanup taxobox}} fail to end up in Category:Taxobox cleanup requests ( 0 ), unlike mainspace articles? — Preceding unsigned comment added by Awkwafaba (talk • contribs) 15:42, 27 November 2021 (UTC)

Because categorization is applied only to pages in article space, per the template's documentation. "Ambox" is short for "article message box". – Jonesey95 (talk) 17:31, 27 November 2021 (UTC)

@Jonesey95: Draft articles are articles, and people have edited {{Don't edit this line}}. How can I ensure that all pages tagged with the template are categorized? --awkwafaba (📥) 05:01, 28 November 2021 (UTC)

What happened when you asked at the talk page for the template, or at Template talk:Don't edit this line, or at Template talk:Automatic taxobox? – Jonesey95 (talk) 06:45, 28 November 2021 (UTC)

@Jonesey95: i asked the template creator, and they didn’t know, because that is me. --awkwafaba (📥) 20:27, 28 November 2021 (UTC)

Draft articles are drafts, they are not articles until they are moved to mainspace and so become part of the encyclopedia. The categories are also suppressed when other cleanup templates - such as {{neutrality}}, {{original research}} or {{unverified}} - are used on drafts. --Redrose64 🌹 (talk) 00:06, 29 November 2021 (UTC)

@Redrose64: so again, how do i change that template behavior. Other templates work on drafts; it’s not universal. --awkwafaba (📥) 02:41, 29 November 2021 (UTC)

The usual way to make a maintenance template apply a category is to add the category to the template code itself, preferably within <includeonly>...</includeonly> tags. YMMV. You'll need to change the word "article" to "page" within the template and its documentation if you do that. – Jonesey95 (talk) 16:16, 29 November 2021 (UTC)