This template is within the scope of WikiProject Infoboxes, a collaborative effort to improve the coverage of Infoboxes on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.InfoboxesWikipedia:WikiProject InfoboxesTemplate:WikiProject InfoboxesInfoboxes
This template is within the scope of WikiProject Historic sites, a collaborative effort to improve the coverage of historic sites on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Historic sitesWikipedia:WikiProject Historic sitesTemplate:WikiProject Historic sitesHistoric sites
This edit request has been answered. Set the |answered= or |ans= parameter to no to reactivate your request.
I made a change to the sandbox to allow for the default image size to be used, and removed the limit on the size of the image. Both make it so that the image is able to be displayed how the user and editor wish, without limiting them. Tests look okay. SWinxy (talk) 04:25, 19 March 2023 (UTC)[reply]
Can we discuss this? The "default size" for infoboxes, while it sounds nice, was never too accurate. Most infoboxes have a default width of 250px, and thus upright=1.14 is a perfect default size. As well, many infoboxes have a max size parameter. No infobox should be wider than 325px, and none really are, but this prevents the many newer editors from making such a mistake, and does no harm otherwise. Can SWinxy provide any cases where these edits actually lead to improvements? ɱ(talk)15:09, 19 March 2023 (UTC)[reply]
So, my settings are to make images 400px wide for reasons. The problem is with infoboxes that think they know a better image size, and will override mine and others' preferences, be they set their preferred size larger or smaller, when there isn't a good rationale for doing so (e.g. important visual elements that can't be scaled along with the image). I've never seen a max size parameter until now, so I would disagree there are 'many' infoboxes with them. The vast majority of infoboxes I deal with don't force an image size. I am suspect of the claim that new editors would change the size of infobox images to be larger than they should. Does this even happen? Do editors not fix that? SWinxy (talk) 19:49, 19 March 2023 (UTC)[reply]
Those project pages disagree with you. MOS:IMGSIZE: Except with very good reason, a fixed width in pixels (e.g. 17px) should not be specified. This ignores the user's base width setting, so upright=scaling factor is preferred whenever possible.WP:IMGSIZE: Except with very good reason, do not use px (e.g. |thumb|300px), which forces a fixed image width measured in pixels, disregarding the user's image size preference setting. They are clear and consistent that the image sizes should be left up to the user unless a very good reason is provided. I'm not sure where you're getting the numbers of 250px, 235px, and 1.14 from; those pages don't mention those values. There are only 85 templates that make use of the maxsize parameter; hardly 'many.' SWinxy (talk) 22:01, 19 March 2023 (UTC)[reply]
This is a failure to read the entire section I linked. MOS:IMGSIZE says "Cases where fixed sizes may be used include for standardization of size via templates (such as within infobox templates or the display of country flag icons), for displaying reduced images sizes where space is constrained (such as..." ɱ(talk)00:09, 20 March 2023 (UTC)[reply]
That's a small carveout exception for other usages so that editors aren't pedantic about templates like {{Flagicon}}. All the other text surmount to "don't use fixed pixel widths". I don't feel that the image use policy needs changing, because it is pretty explicit about not setting a fixed size. SWinxy (talk) 01:56, 20 March 2023 (UTC)[reply]
"Small carveout exception", or in other words, policies and guidelines have small details you literally have to follow. I changed just a few infoboxes, and it looks like people largely agree with me. Several of these, including this case, were actually only restoring defaults that had existed for years and years until they were changed without discussion. ɱ(talk)12:51, 20 March 2023 (UTC)[reply]
Ɱ: Where are all of these people who "largely agree with" you? Many of us have stated our objections to these fixed pixel sizes in multiple discussion over the past year or so. I can't recall anyone agreeing with your interpretation of the guidelines. – Jonesey95 (talk) 17:36, 20 March 2023 (UTC)[reply]
"I can't recall" isn't a good argument. As well, I have plenty of evidence of these parameters in use in extremely-high-use templates, for years to decades before your removals, and some for years after. Nobody else has recently objected enough to try to remove them, except for this user here, who wants them removed "for reasons". ɱ(talk)18:40, 20 March 2023 (UTC)[reply]
I asked for help here, and the guidance was to use |upright= without specifying anything related to px sizes. I think if we just removed the default px and maxsize px, things would work fine. – Jonesey95 (talk) 18:58, 20 March 2023 (UTC)[reply]
Can @Hike395: please pitch in on how to adjust this infobox to allow for scalable images and image maps? I was looking through your changes to the infobox language template. I was hoping we could find a solution without requiring new parameters, or are those optional? I am somewhat confused how that implementation functions. ɱ(talk)19:30, 20 March 2023 (UTC)[reply]
I think {{infobox NRHP}} may work well with the code "|sizedefault=frameless|upright=1.136" (or 1.14). Images scale up with the user preferences set for 400px. ɱ(talk)21:24, 20 March 2023 (UTC)[reply]
I wrote a version in the sandbox which accepts an upright parameter and a fixed size parameter for both |image= and |image_map=
Unfortunately, there's no easy way for pushpin maps (|locmapin=) to accept upright parameters
The upright parameter defaults to 1.14, with a maximum of 1.5
The size parameter has a maximum of 325px. If it is unparsable as a number, it defaults to 250px
I had to add |image_map_upright= to accept an upright parameter for the image map.
If both upright and fixed size parameters are given, the fixed size overrides the upright.
If the maximum size of 325px in the sandbox works, I think it is unnecessary and contrary to MOS. If I have a browser window that is 2000px wide and choose a thumb size in Preferences of 400px because everything else looks too small in comparison to the rest of the page, image declarations should respect that thumb size preference, so the max size in px should be removed. If, on the other hand, the upright value overrides the px value, which it presumably should, then the max px size in the template doesn't do anything and can be removed. I do not have the energy right now to create test cases to see what actually happens. – Jonesey95 (talk) 13:51, 21 March 2023 (UTC)[reply]
_-_The_Noun_Project.svg){kind=small}
Not done: please edit Template:Infobox historic site/doc directly — Martin (MSGJ · talk) 22:29, 12 March 2021 (UTC)
Completed. P.I. Ellsworth , ed. put'er there 13:04, 19 March 2023 (UTC)
Reverted pending discussion. P.I. Ellsworth , ed. put'er there 15:37, 19 March 2023 (UTC)