Module talk:Message box
 | This module was considered for deletion on 2020 February 15. The result of the discussion was "keep". |
 | Module:Message box is permanently protected from editing because it is a heavily used or highly visible module. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit protected}} to notify an administrator to make the requested edit.
|
|
|
|
This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present. |
Protected edit request on 25 June 2024
edit | This edit request to Module:Message box/fmbox.css has been answered. Set the |answered= or |ans= parameter to no to reactivate your request. |
Change fmbox-warning background-color to #300 in night mode for consistency with other mboxes.
Diff:
| − | html.skin-theme-clientpref-night .fmbox-warning {
background-color: | + | html.skin-theme-clientpref-night .fmbox-warning {
background-color: #300; /* Reddish, same hue/saturation as light */
}
@media (prefers-color-scheme: dark) {
html.skin-theme-clientpref-os .fmbox-warning {
background-color: #300; /* Reddish, same hue/saturation as light */
}
}
|
Andumé (talk) 04:52, 25 June 2024 (UTC)
- No opinion on the change request, but presumably if you want to change the bg color, then you'd want to change the comment to match? Mathglot (talk) 18:09, 25 June 2024 (UTC)
- That would probably be a good idea, although those comments are often inaccurate anyway, especially on Module:Message box/cmbox.css. Andumé (talk) 21:30, 25 June 2024 (UTC)
- Shouldn't be inaccurate? The only one I can think of is the blue of one of the specific cmboxes. IznoPublic (talk) 06:48, 8 July 2024 (UTC)
- @Izno: The specific inaccuracy I was thinking of was the cmbox.css's night mode styles refer to #300 as "pink", although that is not the only one. Andumé (talk) 20:29, 14 July 2024 (UTC)
- And in fact cmbox makes no claim about similar hue/saturation that I can see?? Please ensure you're being factual. IznoPublic (talk) 06:50, 8 July 2024 (UTC)
- Shouldn't be inaccurate? The only one I can think of is the blue of one of the specific cmboxes. IznoPublic (talk) 06:48, 8 July 2024 (UTC)
- That would probably be a good idea, although those comments are often inaccurate anyway, especially on Module:Message box/cmbox.css. Andumé (talk) 21:30, 25 June 2024 (UTC)
- The light colors are also not consistent IIRC? Which specific other dark box are you trying to make this consistent with and what is the light color for that box? IznoPublic (talk) 06:48, 8 July 2024 (UTC)
- What I meant with "consistency" was that cmbox's night mode styles (cmbox being the only standard mbox to use colorful backgrounds afaik), for colored backgrounds, use the same background color as the light mode styles, except with a lightness of 10. Also, cmbox-delete and cmbox-speedy both have the same background in light mode as fmbox-warning, and they use #300 as background-color in night mode. I hope this makes sense. Andumé (talk) 20:41, 14 July 2024 (UTC)
- Please don't reactivate the edit request while discussion is ongoing. I'll review this later. Izno (talk) 23:27, 14 July 2024 (UTC)
- What I meant with "consistency" was that cmbox's night mode styles (cmbox being the only standard mbox to use colorful backgrounds afaik), for colored backgrounds, use the same background color as the light mode styles, except with a lightness of 10. Also, cmbox-delete and cmbox-speedy both have the same background in light mode as fmbox-warning, and they use #300 as background-color in night mode. I hope this makes sense. Andumé (talk) 20:41, 14 July 2024 (UTC)
Done After looking at this and consistency among other templates, 300 is as fine as anything. Probably it would make sense to regularize the cmbox deletion colors and the fmbox warning color to match the deletion colors for all other templates in both light and dark mode, which is currently at fee7e6 for the speedy background and 310402 speedy dark background. And to reconsider that cmbox has colored backgrounds. Izno (talk) 21:58, 3 August 2024 (UTC)
Urgent: Please fix this template for printed content Module:Message box/ombox.css.
editFirstly, apologies for writing in English if this is not your first language (this is an automated message).
This template has been detected as one of 436 pages using styles that break the page when printed when the user is using dark mode. The fix is very straightforward - all your styles relating to dark mode must be scoped to. Since there is a high risk of this templates being copied to other wikis it is important this notice is acted on ASAP.
To fix this:
- Update `@media (prefers-color-scheme: dark` to `@media screen and (prefers-color-scheme: dark`
- Wrap any styles relating to `html.skin-theme-clientpref-night` in `@media screen`
If this message has not been acted on in 7 days, this will be fixed by an automated script. Thank you for your help fixing this important issue.
For any questions feel free to ask them at phab:T369874.
Jon (WMF) (talk) 18:22, 2 August 2024 (UTC) on behalf of the web team.
- Done. Izno (talk) 22:02, 3 August 2024 (UTC)
Protected edit request on 13 September 2024
edit | It is requested that an edit be made to the fully protected module at Module:Message box. (edit · history · last · links · sandbox · edit sandbox · sandbox history · sandbox last edit · sandbox diff · test cases · transclusion count · protection log) This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.
Edit requests to fully protected pages should only be used for edits that are either uncontroversial or supported by consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the module's sandbox and test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a protection request. When the request has been completed or denied, please add the |
Add |imageclass=, |imageleftclass=, and |imagerightclass= parameters as done in the sandbox at Special:Diff/1245579475. This will allow classes such as skin-invert to easily be added to the images. --Ahecht (TALK
PAGE) 20:46, 13 September 2024 (UTC)
Please add param class
edit| | It is requested that an edit be made to the fully protected module at Module:Message box. (edit · history · last · links · sandbox · edit sandbox · sandbox history · sandbox last edit · sandbox diff · test cases · transclusion count · protection log) This template must be followed by a complete and specific description of the request, so that an editor unfamiliar with the subject matter could complete the requested edit immediately.
Edit requests to fully protected pages should only be used for edits that are either uncontroversial or supported by consensus. If the proposed edit might be controversial, discuss it on the protected page's talk page before using this template. Consider making changes first to the module's sandbox and test them thoroughly here before submitting an edit request. To request that a page be protected or unprotected, make a protection request. When the request has been completed or denied, please add the |
Please add parameter |class=, so that those message boxes that were enabled for it, could pass the parameter to allow user styling, including turning off the box.
My use case is the issue of banner clutter on article talk pages, where there have been disputes about placement of many non-compulsory banners. The easiest way to handle this imho would be to permit the user to enter .banner-foo {display:none} in their common.css, applying it to a class passed in the message box but for that to work we need to have the class available in the box as a parameter. Imho, having this available would reduce the strife about talk page banners that seems to be a perennial issue; those most perturbed could simply turn them off individually. It should be clear that this feature would not permit users to arbitrarily turn off any banner, only those which had the passed the param through (via |class={{{class|}}}) in the *mbox template, and only one by one; so that it would allow adding, say, a |class= param to the {{Tmbox}} for Template:Talk header to allow it to be turned off, but not to an ArbCom template. Those templates are already mostly edit protected anyway, so there shouldn't be any problem with editors maliciously adding a class to an mbox where they shouldn't. (Full disclosure: I generally want to see all message boxes and wouldn't use the feature; I am interested in having it to reduce the disputes and wasted time about the topic by offering it to those who oppose them, and who are sufficiently motivated to go to the point of adjusting their common.css, which should quiet the disputes and keep everybody happy.) Mathglot (talk) 20:48, 14 September 2024 (UTC)
Listed: at WP:Village pump (proposals). Mathglot (talk) 20:44, 16 September 2024 (UTC)
- I think an opt-in strategy might be better at allaying editor concerns about too many messages. If the message box is designated as a hidden message box, a general class could be added, with a rule that hides content with that class. A parameter could be used to provide a custom class, so someone could create a personal CSS rule to display messages that specified the custom class. Editors who want to see all the hidden messages would just need a personal rule for the general class. isaacl (talk) 22:22, 16 September 2024 (UTC)