[01:30:00] <MirahezeRelay>	 <wickerbasket2540> Congrats, Sakura!
[05:09:23] <MirahezeRelay>	 <pixldev> @jenny_on_wiki any thoughts on removing the brackets from assistant steward on https://meta.miraheze.org/wiki/Module:Staff_timeline2/config, feel a bit weird to me/like it's referring to AS and Stewards collectively
[05:10:07] <MirahezeRelay>	 <pixldev> also why is GP not on this page guh
[06:34:16] <MirahezeRelay>	 <sakurababochka, replying to wickerbasket2540> Thanks!
[08:15:53] <MirahezeRelay>	 <enzimar> [1/2] https://cdn.discordapp.com/attachments/1225560610628964423/1557667837588283493/image.jpg?ex=6ac8a2b8&is=6ac75138&hm=0967c65d2a91fcb1d9683b3c8d939a69aa295465b839f3a72427ac70a7bd5148&
[08:15:53] <MirahezeRelay>	 <enzimar> [2/2] https://cdn.discordapp.com/attachments/1225560610628964423/1557667837999321128/image.jpg?ex=6ac8a2b8&is=6ac75138&hm=3cf0b1003c62dfa68b8b629f5a3664fd5190645c9c0b233b4e359777ac62308b&
[12:45:11] <MirahezeRelay>	 <jenny_on_wiki, replying to pixldev> well there isn't a graph where that would make a difference; the gp chart just refers to them as "former" and "current"
[15:33:21] <MirahezeRelay>	 <pixldev> fair
[16:43:43] <MirahezeRelay>	 <akcentgamez> Hey does anyone want to give feedback on a site I made to help people learn wiki text (currently made for the rt3 wiki) and had ai assistance
[17:25:58] <MirahezeRelay>	 <uranium_mandy, replying to akcentgamez> We can't give feedback unless you send us a link - #verify to get permission to send links
[18:01:43] <MirahezeRelay>	 <posix_memalign> Repeating this since I think it's something very useful but I have many other tasks on my plate right now.
[18:05:26] <MirahezeRelay>	 <aeywoo, replying to posix_memalign> Sounds like a good idea.
[18:07:44] <MirahezeRelay>	 <posix_memalign> Yeah we just need to get the discussion started on Meta but I have an ever increasing backlog unfortunately.
[18:08:23] <MirahezeRelay>	 <raidarr> even if its vector legacy imo do not enable although that is partially selfish from me
[18:09:08] <MirahezeRelay>	 <raidarr> a variation that might be useful is 'enable for new' given there is a current of thought that dislikes imposition of change on existing projects and there is often precedence for that approach
[18:11:27] <MirahezeRelay>	 <posix_memalign> [1/2] Yeah it makes sense. Just harder on the technical side to auto-enable MF/MN only on new wikis that change the default skin to vector legacy.
[18:11:27] <MirahezeRelay>	 <posix_memalign> [2/2] Maybe a help message for the default skin configuration is appropriate. And in general perhaps we should link our guides on Meta more in ManageWiki settings.
[18:13:42] <MirahezeRelay>	 <aeywoo> Maybe enabling Capiunto or InfoboxNeue by default would be a good idea too, since almost every wiki uses them, either they're used to them from Fandom, or they want to Lua-fy their infoboxes.
[18:14:19] <MirahezeRelay>	 <sakurababochka> Isn't it PortableInfobox that people use when they're coming from fandom?
[18:21:20] <MirahezeRelay>	 <posix_memalign> [1/2] Yeah I think PI gets used much more often. Capiunto seems less useful since it just provides a Lua library, so it doesn't even need to be an extension.
[18:21:21] <MirahezeRelay>	 <posix_memalign> [2/2] InfoboxNeue seems to be a SCT module so it could possibly belong to Loadout Wiki but not as a default extension.
[18:47:13] <MirahezeRelay>	 <notaracham, replying to posix_memalign> The way of things. 🥲
[19:07:43] <MirahezeRelay>	 <emiliers> As an advocate for TemplateData, I can try writing something up for it if no one else is interested... Might be a bit before I can find the time tho
[19:09:57] <MirahezeRelay>	 <jenny_on_wiki> tbh I don't know why you wouldn't want TemplateData
[19:17:23] <MirahezeRelay>	 <posix_memalign, replying to emiliers> Might take a while on my side as well, so I guess we'll see who beats everyone else to it. After the initial page is created it'll be a lot easier to add more proposals.
[19:54:06] <MirahezeRelay>	 <raidarr> its probably an easy one to add as default, I'd have to stretch for reasons why not like if it has some kind of performance impact or maybe adds interface clutter or something
[22:37:51] <MirahezeRelay>	 <eri_nyuhuhu, replying to posix_memalign> Wanted to chip in that responsive Vector 2022 doesn't work so well on certain orientations of mobile devices like the iPad Mini in portrait mode as it forces a zoom out. It's probably a WebKit quirk, but it also doesn't happen on MinervaNeue... 🤔
[22:39:23] <MirahezeRelay>	 <person0192837465, replying to eri_nyuhuhu> can you share a link and what caused the zoom out? (maybe an OS version too since I don't have my phone updated atm), I can open devtools for the site and poke around a bit
[23:28:14] <MirahezeRelay>	 <posix_memalign, replying to eri_nyuhuhu> [1/3] Thanks for the feedback. If you tested on Stella Sora Wiki, it'll work suboptimally since `$wgVectorResponsive` is off. This is turned on for new wikis so their experience would be better.
[23:28:14] <MirahezeRelay>	 <posix_memalign, replying to eri_nyuhuhu> [2/3] I had a few other gripes with Vector 2022 as well. The WMF's priority on fixing Vector 2022 issues on mobile is low because only a few wikis hosted by them use Vector 2022 for mobile.
[23:28:15] <MirahezeRelay>	 <posix_memalign, replying to eri_nyuhuhu> [3/3] Though I think with the amount of trouble MobileFrontend has caused (e.g. parsing a page differently which causes inconsistent page output between desktop and mobile, removing elements with certain classes such as `.navbox` by default), we should go with the less broken option.
[23:29:37] <MirahezeRelay>	 <eri_nyuhuhu> So I wrote up a reproduction, but then forgot to press send. Oops.
[23:36:40] <MirahezeRelay>	 <eri_nyuhuhu> [1/18] Can reproduce here on Public Test Wiki and Wikipedia
[23:36:40] <MirahezeRelay>	 <eri_nyuhuhu> [2/18] https://publictestwiki.com/wiki/Category:Non-test%20pages?useskin=vector-2022
[23:36:40] <MirahezeRelay>	 <eri_nyuhuhu> [3/18] https://en.wikipedia.org/wiki/Main_Page?useskin=vector-2022
[23:36:41] <MirahezeRelay>	 <eri_nyuhuhu> [4/18] Doesn't happen on:
[23:36:41] <MirahezeRelay>	 <eri_nyuhuhu> [5/18] https://publictestwiki.com/wiki/Category:Non-test%20pages?useskin=minerva
[23:36:41] <MirahezeRelay>	 <eri_nyuhuhu> [6/18] https://wikipedia.org/wiki/Main_Page?useskin=minerva
[23:36:42] <MirahezeRelay>	 <eri_nyuhuhu> [7/18] iPadOS 27.0 (24A437)
[23:36:42] <MirahezeRelay>	 <eri_nyuhuhu> [8/18] iPad Mini 6
[23:36:42] <MirahezeRelay>	 <eri_nyuhuhu> [9/18] There's a newer hot fix (27.0.1) available that I haven't installed yet, so maybe I'll try reproducing after that again
[23:36:43] <MirahezeRelay>	 <eri_nyuhuhu> [10/18] Steps:
[23:36:43] <MirahezeRelay>	 <eri_nyuhuhu> [11/18] - Navigate to either page in landscape orientation
[23:36:44] <MirahezeRelay>	 <eri_nyuhuhu> [12/18] - Rotate the device to portrait
[23:36:44] <MirahezeRelay>	 <eri_nyuhuhu> [13/18] Expected behaviour: it scales properly to the device and the text and controls don't become unusably small without zooming in
[23:36:45] <MirahezeRelay>	 <eri_nyuhuhu> [14/18] Actual behaviour: it zooms out, making the controls hard to hit without zooming in and text uncomfortable to read
[23:36:45] <MirahezeRelay>	 <eri_nyuhuhu> [15/18] https://cdn.discordapp.com/attachments/1225560610628964423/1557899555675176990/ScreenRecording_10-08-2026_17-36-03_1.mp4?ex=6ac97a86&is=6ac82906&hm=df49de41f1aafde467c4efb6e7187b49f2d9cc7c5d98ed978c643105e1cfa70a&
[23:36:46] <MirahezeRelay>	 <eri_nyuhuhu> [16/18] https://cdn.discordapp.com/attachments/1225560610628964423/1557899556862034031/ScreenRecording_10-08-2026_17-35-36_1.mp4?ex=6ac97a86&is=6ac82906&hm=94d10aa3676f14d41fdffa66554f385dbdb5c675b436af8e59b9b5b3110ccbee&
[23:36:46] <MirahezeRelay>	 <eri_nyuhuhu> [17/18] https://cdn.discordapp.com/attachments/1225560610628964423/1557899558305009714/ScreenRecording_10-08-2026_17-34-10_1.mp4?ex=6ac97a87&is=6ac82907&hm=5f524bd8367b0d2fadade576f613a8304549c3812a85cb55edd5300b7b9fb64f&
[23:36:47] <MirahezeRelay>	 <eri_nyuhuhu> [18/18] https://cdn.discordapp.com/attachments/1225560610628964423/1557899559806574593/ScreenRecording_10-08-2026_17-33-51_1.mp4?ex=6ac97a87&is=6ac82907&hm=96427978de41f5ac6b3fdce317c16022d6117eae41cac6c3c9ce4f1e247ca9eb&
[23:37:15] <MirahezeRelay>	 <eri_nyuhuhu> So it's an upstream issue, but I think it would still affect usability for mobile users.
[23:38:30] <MirahezeRelay>	 <posix_memalign, replying to eri_nyuhuhu> Could you try on https://strinova.org ? I think it has the right config for this.
[23:39:40] <MirahezeRelay>	 <eri_nyuhuhu, replying to posix_memalign> Works properly here, that's interesting. What configuration differences does it have?
[23:40:02] <MirahezeRelay>	 <posix_memalign> `$wgVectorResponsive`, which we enabled for new wikis a while back
[23:40:40] <MirahezeRelay>	 <posix_memalign> So recent wikis like https://kmckingdomsmc.miraheze.org which was created in September 16 would also be free of this issue
[23:40:53] <MirahezeRelay>	 <janebuzjane> Dappervolk Wiki also has responsive mode for Vector 2022 turned on if that is helpful to test: <https://dappervolk.miraheze.org>
[23:45:24] <MirahezeRelay>	 <eri_nyuhuhu> Works properly on all of those,  interesting