but it would be even better if it didn't output anything at all. [20:25:07] This is so I can have a bunch of {{#vardefine:...}} on separate lines without leading to a bunch of empty lines being output... [20:28:44] taylan: Try: {{ns:0|put text to be parsed here}} [20:29:08] I'm not sure if the parser will detect there will be no output at all and omit parsing it... [20:31:21] parser isn't smart enough for that, it'd depend on how the magic word was defined (i.e. if it takes parsed args or unparsed args) [20:47:06] wow that actually works [20:58:52] that's a good trick [20:59:22] a template with no output would also work, but ns:0 is empty :D [21:03:48] For some reason a template that takes no args and produces no output didn't work. I have a {{blank}} template that's just a shorthand for which we use for whitespace tricks, and {{blank|text goes here}} didn't work... [21:04:23] Perhaps because unused template args aren't evaluated, whereas the ns magic word functions differently... [21:07:22] template probably evaluates parameters but doesn't parse wikitext. That gets delayed until the end, and since the parameter 0 isn't on the output, the wikitext doesn't get parsed. But that magic word seems to work differently [21:08:06] I wouldn't be surprised if it stopped working at one point [21:09:03] {{ns: }} doesn't _need_ to parse any extra argument [21:09:05] whether a magic word parses all of its arguments or not is dependent on whether SFH_OBJECT_ARGS is present as a flag in the magic word definition; if it it's *not* present (the default), then all args are parsed before being passed to the magic word's PHP callback [21:09:21] if present, the PHP callback would be responsible for parsing the args it cares about itself [21:10:37] I wouldn't be surprised to see most/all core magic words shifting to object args at some point in time in the future either [21:11:36] hmm, any alternative that's sure to keep working? [21:12:21] * moonmoon only knows this because he was digging through the parser/preprocessor code yesterday to see how feasible it'd be to make something that took arbitrary args (including the same arg multiple times) and expose all passed values and the exact ordering of args to scribunto [21:13:37] taylan: pretty much impossible to see into the future, so do what works now and keep an eye on deprecation notices. Something that impacts wikitext parsing is sure to be discussed at length before it'd be implemented [21:13:51] all right [21:13:52] I don't know about other methods. {{#if:|text to be parsed without output}} won't work, for example [21:14:40] how about invoking a no-op Lua module? [21:15:16] what about {{#if: |||}} ? [21:15:28] that'd probably work, yeah [21:15:32] that... is smart lol [21:16:02] one too many pipes, not that that harms anything [21:16:34] yep, I added too many pipes :D [21:16:55] Hmm, I already have Template:Trim which is {{#if: {{{1|}}} | {{{1}}} }} and the name is very fitting, so I could just use that. [21:17:45] Works beautifully [21:25:18] You know what would be rad though? A way to tell the parser to just strip all blank lines. Like, if it would insert

, don't insert anything at all. [23:12:07] Can I set in my Commons.js or Commons.css page that the maximum width of the skin vector 2022 is default? $wgVectorMaxWidthOptions https://www.mediawiki.org/wiki/Skin:Vector/2022 [23:12:17] (for wikivoyage wiki) [23:13:20] you can't change $wg configuration from css or js, if that is what you were getting at [23:13:47] :( [23:14:04] hack? [23:15:45] you may be able to get the same with css [23:16:53] I don't know how to modify that, I just steal/copy the code from other wiki places. [23:17:02] :! [23:20:23] you want to enable or disable it? [23:21:42] I don't understand why it's designed so complex [23:22:50] you probably want to override this: [23:22:51] https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/skins/Vector/+/refs/heads/master/resources/skins.vector.styles/layouts/grid.less#64 [23:27:04] Changing the subject, do you like the way es.wikivoyage.org main page loads? my connection is bad and sometimes it is still slow. There is a related Phab task. [23:32:45] it loads in 14.81 s here [23:32:56] DOMContentLoaded in 5.13s [23:33:45] https://upload.wikimedia.org/wikipedia/commons/2/2f/Cabo_de_Gata_-_las_salinas_de_San_Miguel_%28cropped%29.jpg is a 4.76 MB download ... [23:35:58] I don't remember that in Commons there is a tool that removes "weight" from the images or yes? it is that sometimes the only good image to use is heavy or even the only one. [23:38:36] well, you could scale the image [23:39:02] I think you are doing some zooming there, so not sure which size you really need [23:39:32] the whole page is 8.48/7.68 MB transferred, so half the page weight is that image [23:39:41] there may be ways to lazy-load it [23:40:06] Yes, but the downside is that it takes away from the relevant picture of the "featured banner" by focusing on a part that doesn't count for much. [23:40:10] hum [23:40:51] I suspect you don't need the image to be *that* big [23:41:05] while it can still be provided in a large size [23:41:13] it would require some investigation, though [23:42:03] This is how a retired editor designed it. [23:42:15] 16:9 [23:42:33] https://es.wikivoyage.org/wiki/Wikiviajes:P%C3%A1gina_principal/Gu%C3%ADa_de_uso#Selecci%C3%B3n_de_im%C3%A1genes [23:43:31] how many people is going to browse the site in 16:9 ? [23:43:33] O_o [23:45:08] All Wikivoyage banners have a similar style 7:1, https://es.wikivoyage.org/wiki/Ayuda:Banners [23:46:03] Almost all Wikivoyages have the same on Main Page [23:47:04] Hey, maybe a request can be started on phab to create "extendedconfirmed" protection level for eswiki?