126:
22:
660:
71:
53:
673:
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
422:
I agree with Anomie here, the issue is more specific. This particular issue is: there are 100k pages using a class in a table "ad hoc" and we don't have anything currently in
TemplateStyles that does similar on that many pages, and there's been at least some discussion prior that we could have issues
548:
mean that - where possible - style rules in sitewide CSS should be moved to the
TemplateStyles of the relevant templates? Only asking as it occurred to me that it could potentially also refer to changing the content model of all sitewide CSS files to TemplateStyles/moving all sitewide CSS rules to a
630:
Yes, and as I've said already, I think both 1) their warning is bunkum (a different WMF engineer said this use is kosher!), and 2) the fix on our part is trivial (in two different ways, the first is putting templatestyles tags directly in article wikitext and the second is just putting the CSS back
567:
it is meant to mean something like "when things are meant to display on every page, they should be in the sitewide style. If it is not something for the entire site and can feasibly be done by a template/with
TemplateStyles, it should." I have amended the question for clarity (by adding the words
219:
element? I understand the need to avoid malicious code, but if it were managed similar to gadgets by someone with higher permissions, then I would think it's possible. Ideally, MediaWiki would just do this to all tables (not just sortable) making this script and the same move done in the sticky
648:
423:
down the road (which I think are negligible - the fix would be "re-add the CSS to Common.css"). There is clear consensus that moving stuff from global CSS to
TemplateStyles is beneficial, otherwise the quantity of CSS already removed from
471:
I'm not buying the argument that the community can't get edits made. First, any of these pages that are massively used are going to end up admin-protected anyway - and most admins aren't going to try to touch a SCSS page. Also,
650:
496:
has been a key champion of this trend. Not sure there really is a problem to solve right now? For example, there is pretty much no chance we'd add any new template specific styling to sitewide scripts these days. —
603:
We should not make use of such functionality so as to not end up in a position where another migration would be needed if said functionality is removed, which would prohibit uses like the one proposed in
601:
Styles included by a template can currently affect content on the page outside of the content generated by that template, but this ability may be removed in the future and should not be relied upon.
699:
395:
the first time a bot is "implementing" TemplateStyles this way places this BRFA as a precedent and puts an even larger onus on BAG to establish a clear consensus for the task
311:
719:
605:
357:
724:(And in hindsight I apologize for the terrible RfC question I asked six months ago; re-reading it I am wondering why I thought that would help. Live and learn.)
562:
550:
473:
280:
would also benefit from the same move, but its "no-JS" version would be problematic. MediaWiki moving the rows without JS would be the best solution.
297:
338:
688:
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.
631:
in Common.css if it's necessary), and 3) we already have other templates (like the one literally 2 sections above) doing the exact same thing.
381:
I don't see how this RFC would do anything to un-stall that BRFA. The questions there are far more specific than "is
TemplateStyles good?".
349:
588:
555:
549:
fully-protected
TemplateStyles page. (It might just be me who's confusing themselves with the wording, though!) All the best, —
376:
139:
482:
393:
My read of the discussion is that it was stalled (well, besides the fact that the bot operator went inactive) because it was
664:
625:
430:
Suggest removing the RFC tag for now and just getting all the types of editors on this page discussing the actual problem.
414:
388:
289:
248:
87:
741:
503:
460:
201:
or anyone else. I'm not seeing much documentation on template scripts, so I'm asking here. Can a script be added to the
730:
577:
532:
449:
403:
365:
327:
319:
229:
521:
640:
439:
512:
Indeed. Take a look at what the BRFA linked by House wanted to do and then feel free to give an opinion on that.
83:
78:
58:
670:
Firstly, apologies for writing in
English if this is not your first language (this is an automated message).
620:
33:
596:
274:
236:
169:
595:
The question is too broad. Generally, TemplateStyles should be preferred; however, the developers have
315:
260:
Thanks for the quick response. Seems like it would work once available. The "no-JS fallback" for
737:
705:
584:
456:
410:
372:
334:
285:
264:
225:
205:
716:
Should bots be permitted to make edits in support of migrating sitewide CSS to
TemplateStyles?
681:
Update `@media (prefers-color-scheme: dark` to `@media screen and (prefers-color-scheme: dark`
39:
424:
86:. If you would like to participate, please visit the project page, where you can join the
8:
695:
181:
727:
574:
539:
446:
400:
362:
324:
312:
Knowledge:Village pump (idea lab)#Getting plainrowheaders out of MediaWiki:Common.css
281:
221:
599:
certain cases where
TemplateStyles current functionality should not be relied upon.
152:
614:
385:
243:
718:
be a helpful RFC question? I believe such a question would if successful unfreeze
398:
684:
Wrap any styles relating to `html.skin-theme-clientpref-night` in `@media screen`
722:
while also avoiding RfC after RfC on similar issues (if we need further bots).
691:
636:
517:
435:
302:
Should
TemplateStyles be officially preferred (where possible) to sitewide CSS
270:
would simply be nothing sticky, similar to sortable tables not being sortable.
188:
148:
509:
498:
477:
353:
125:
609:
382:
356:) and allows for faster load times. If successful, this would greenlight
255:
240:
196:
154:
192:
632:
513:
491:
431:
427:
would be in violation of that implicit but otherwise clear consensus.
711:
150:
487:
FWIW there's been a rather consistent trend of moving common-: -->
235:
This is not possible right now, but it may be possible soon with
70:
52:
82:, a group dedicated to improving the maintenance of Knowledge's
352:. In particular, it allows more people to edit "sitewide" CSS (
155:
397:. I think this discussion would clearly resolve that concern.
714:, I think it is time to revisit this. Would something like
720:
Knowledge:Bots/Requests for approval/William Avery Bot 5
606:
Knowledge:Bots/Requests for approval/William Avery Bot 5
649:
Urgent: Please fix this template for printed content
474:
Category:Knowledge interface-protected edit requests
119:
651:
Template:TemplateStyles sandbox/Sohom/altstyles.css
350:
MediaWiki talk:Common.css/to do#Description of work
712:#RfC: converting sitewide CSS to TemplateStyles
298:RfC: converting sitewide CSS to TemplateStyles
348:as proposer, for all the reasons outlined in
163:This page has archives. Sections older than
32:does not require a rating on Knowledge's
674:important this notice is acted on ASAP.
173:when more than 4 sections are present.
665:Template talk:TemplateStyles sandbox
21:
19:
15:
38:It is of interest to the following
13:
320:Knowledge:Village pump (technical)
14:
752:
167:may be automatically archived by
76:This page is within the scope of
658:
306:? 15:30, 21 February 2024 (UTC)
124:
69:
51:
20:
96:Knowledge:WikiProject Templates
99:Template:WikiProject Templates
1:
710:Six months after the aborted
641:05:24, 22 February 2024 (UTC)
626:04:36, 22 February 2024 (UTC)
589:17:27, 21 February 2024 (UTC)
556:17:18, 21 February 2024 (UTC)
522:18:42, 21 February 2024 (UTC)
504:18:18, 21 February 2024 (UTC)
483:15:47, 21 February 2024 (UTC)
461:18:13, 21 February 2024 (UTC)
444:Happy to remove the RfC tag.
440:17:47, 21 February 2024 (UTC)
415:17:42, 21 February 2024 (UTC)
389:17:27, 21 February 2024 (UTC)
377:15:30, 21 February 2024 (UTC)
339:15:30, 21 February 2024 (UTC)
290:23:04, 16 February 2024 (UTC)
249:22:08, 16 February 2024 (UTC)
230:21:21, 16 February 2024 (UTC)
215:to move header rows into the
213:.sticky-header:not(.sortable)
90:and see a list of open tasks.
7:
742:23:48, 19 August 2024 (UTC)
702:on behalf of the web team.
237:Knowledge:On-demand gadgets
10:
757:
700:17:54, 2 August 2024 (UTC)
656:
544:For clarification, would
316:MediaWiki talk:Common.css
64:
46:
570:for non-sitewide styling
476:is rarely backlogged. —
360:and other related work.
358:this stalled bot request
304:for non-sitewide styling
170:Lowercase sigmabot III
79:WikiProject Templates
546:officially preferred
425:MediaWiki:Common.css
706:Sitewide CSS, again
275:Static row numbers
102:Templates articles
34:content assessment
725:
624:
536:
341:
220:gadget obsolete.
177:
176:
118:
117:
114:
113:
110:
109:
748:
733:
723:
662:
661:
612:
580:
566:
543:
530:
501:
495:
480:
452:
417:
406:
368:
330:
309:
279:
273:
269:
263:
259:
218:
214:
210:
204:
200:
182:Template scripts
172:
156:
128:
120:
104:
103:
100:
97:
94:
73:
66:
65:
55:
48:
47:
25:
24:
23:
16:
756:
755:
751:
750:
749:
747:
746:
745:
731:
708:
668:
667:
659:
655:
578:
560:
554:
537:
533:Summoned by bot
499:
489:
478:
450:
404:
366:
342:
328:
305:
300:
277:
271:
267:
261:
253:
246:
245:it has begun...
216:
212:
208:
202:
186:
184:
168:
157:
151:
133:
101:
98:
95:
92:
91:
12:
11:
5:
754:
707:
704:
686:
685:
682:
657:
654:
647:
646:
645:
644:
643:
593:
592:
591:
563:A smart kitten
553:
551:a smart kitten
528:
527:
526:
525:
524:
469:
468:
467:
466:
465:
464:
463:
428:
419:
418:
308:
303:
299:
296:
295:
294:
293:
292:
244:
217:<thead: -->
183:
180:
175:
174:
162:
159:
158:
153:
149:
147:
144:
143:
135:
134:
129:
123:
116:
115:
112:
111:
108:
107:
105:
74:
62:
61:
56:
44:
43:
37:
26:
9:
6:
4:
3:
2:
753:
744:
743:
739:
735:
734:
729:
721:
717:
713:
703:
701:
697:
693:
689:
683:
680:
679:
678:
677:To fix this:
675:
671:
666:
652:
642:
638:
634:
629:
628:
627:
622:
619:
616:
611:
607:
602:
598:
594:
590:
586:
582:
581:
576:
571:
564:
559:
558:
557:
552:
547:
541:
534:
529:
523:
519:
515:
511:
507:
506:
505:
502:
493:
486:
485:
484:
481:
475:
470:
462:
458:
454:
453:
448:
443:
442:
441:
437:
433:
429:
426:
421:
420:
416:
412:
408:
407:
402:
396:
392:
391:
390:
387:
384:
380:
379:
378:
374:
370:
369:
364:
359:
355:
351:
347:
344:
343:
340:
336:
332:
331:
326:
321:
317:
313:
307:
291:
287:
283:
276:
266:
265:sticky header
257:
252:
251:
250:
247:
242:
238:
234:
233:
232:
231:
227:
223:
211:template for
207:
206:sticky header
198:
194:
190:
179:
171:
166:
161:
160:
146:
145:
142:
141:
137:
136:
132:
127:
122:
121:
106:
89:
85:
81:
80:
75:
72:
68:
67:
63:
60:
57:
54:
50:
49:
45:
41:
35:
31:
27:
18:
17:
726:
715:
709:
690:
687:
676:
672:
669:
617:
600:
597:documentated
573:
569:
545:
540:HouseBlaster
445:
399:
394:
361:
345:
323:
301:
282:Jroberson108
222:Jroberson108
185:
178:
164:
138:
130:
77:
40:WikiProjects
30:project page
29:
740:· he/they)
663:Moved from
488:ts already
587:· he/him)
459:· he/him)
413:· he/him)
375:· he/him)
337:· he/him)
310:Notified:
241:* Pppery *
88:discussion
692:Jon (WMF)
189:Redrose64
93:Templates
84:templates
59:Templates
510:Xaosflux
500:xaosflux
479:xaosflux
131:Archives
732:Blaster
579:Blaster
451:Blaster
405:Blaster
367:Blaster
346:Support
329:Blaster
195:, and
165:60 days
610:JJMC89
383:Anomie
354:WP:5P3
256:Pppery
197:Pppery
36:scale.
728:House
575:House
447:House
401:House
363:House
325:House
193:TheDJ
28:This
738:talk
696:talk
637:talk
633:Izno
608:. —
585:talk
518:talk
514:Izno
492:Izno
457:talk
436:talk
432:Izno
411:talk
373:talk
335:talk
286:talk
226:talk
572:).
698:)
639:)
520:)
438:)
322:.
318:,
314:,
288:)
278:}}
272:{{
268:}}
262:{{
239:.
228:)
209:}}
203:{{
191:,
736:(
694:(
653:.
635:(
623:)
621:C
618:·
615:T
613:(
583:(
565::
561:@
542::
538:@
535:)
531:(
516:(
508:@
494::
490:@
455:(
434:(
409:(
386:⚔
371:(
333:(
284:(
258::
254:@
224:(
199::
187:@
140:1
42::
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
