[13:24:39] <perryprog>	 Is anyone aware (or able to check) if the iOS Wikipedia app supports Dynamic Type? (The global font size setting in the Settings > Accessibility area, if I recall correctly.)
[13:24:46] <perryprog>	 Context is a tech support VRT ticket.
[13:30:22] <MatmaRex>	 perryprog: i guess i can check, what exactly do you need?
[13:31:21] <perryprog>	 Just whether or not it works. The ticket is saying that the text is too small to read but that have settings for larger fonts (which I assume is dynamic type that they're referring to)
[13:32:42] <MatmaRex>	 perryprog: it seems to work for me, but only after restarting the app. give me a minute and i'll share some screenshots
[13:32:52] <perryprog>	 That would be perfect.
[13:46:54] <MatmaRex>	 perryprog: screenshots here: https://phabricator.wikimedia.org/M321/1064/ (there's a gallery below the big image)
[13:47:45] <perryprog>	 Oh, wow. Thank you so much—I can't quite check easily right now so I figured I'd ask here, but that's certainly way more helpful than I was expecting :)
[13:49:58] <MatmaRex>	 i had some trouble with the images, i thought it'd be quicker to do ;) but i figured you don't have an apple devices but need the details
[13:51:31] <perryprog>	 I probably should've said that I do have some... sorry if I caused you any extra trouble
[13:52:35] <perryprog>	 Though I did now learn that Phabricator can host images
[14:12:06] <majavah>	 phabricator can do pretty much everything
[14:21:29] <perryprog>	 Another weird question (going through the VRT tech-issues backlog :P): does anyone know why the language links on kowiki were moved to the top-right instead of the bottom-left area (at least on Vector)?
[14:21:42] <perryprog>	 Compare https://ko.wikipedia.org/wiki/리비아탄_멜빌레이 and https://en.wikipedia.org/wiki/Livyatan for instance
[14:23:42] <majavah>	 perryprog: kowiki has https://www.mediawiki.org/wiki/Reading/Web/Desktop_Improvements turned on by default
[14:23:52] <p858snake>	 https://ko.wikipedia.org/wiki/리비아탄_멜빌레이?uselang=en they look to be in the old spot for me, it might be a gadget or something
[14:24:04] <p858snake>	 or something with newvector
[14:24:43] <p858snake>	 oh I see which bit your talking about now
[14:25:39] <perryprog>	 majavah aha!
[14:25:57] <perryprog>	 Yeah, that's it. Thank you!
[20:56:55] <strainu>	 Hey folks. Today, out of the blue, the mobile Wikipedia site started to look weird. By that, I mean some elements had a desktop-like width, while others remain as usual on mobile. Here is a screenshot: https://imgur.com/a/ktrnESW
[20:56:55] <strainu>	 I tried all the usual debugging techniques: different browser, private window, signing off then back on, disabling all the gadgets, beta options and user scripts. None had any effect when logged in. However, that only happens on my phone (2340x1080 resolution). When testing on laptop in responsive mode (with smaller resolution) the site looks fine.
[20:56:56] <strainu>	 Since the site looks fine when signed out, I assume this is not a software bug so I'm not logging a phabricator issue just yet. Could this be an a/b test where I ended up in the pool I don't like? If not, how could I find the culprit? 
[20:57:40] <Spookreeeno>	 strainu: any idea on the time
[20:59:33] <mutante>	 it could still be a bug that was introcuded in a CSS change
[20:59:34] <strainu>	 Afternoon EEST... so maybe between 11 and 13 UTC?
[20:59:48] <mutante>	 the difference between logged in and logged out could be caching
[21:00:00] <Spookreeeno>	 mutante: I'm thinking that too
[21:00:11] <Spookreeeno>	 That would be early though
[21:00:16] <mutante>	 you could try to find the mobile app repo and search for things merged recently
[21:01:27] <Spookreeeno>	 It's too early for train to be doing anything strange
[21:03:22] <mutante>	 did you ever opt-in into any beta things in your user settings?
[21:03:32] <Spookreeeno>	 Logged out user would be cached though
[21:03:36] <strainu>	 yes, but I have them all disabled currently
[21:03:40] <mutante>	 just thinking more why it could be different when logged in
[21:03:42] <mutante>	 ok
[21:04:00] <Spookreeeno>	 mutante: don't we cache stuff depending on if you're logged in?
[21:04:07] <mutante>	 more likely it's about what can be cached and what cant in our caching layer
[21:04:10] <mutante>	 yea
[21:04:31] <Spookreeeno>	 But I don't understand why it's become an issue at that time
[21:04:32] <mutante>	 if it wasn't mobile I would say to try reloading while holding shift 
[21:04:53] <AntiComposite>	 what device are you using
[21:04:55] <AntiComposite>	 ?
[21:05:03] <strainu>	 Oneplus 6T
[21:05:08] <Spookreeeno>	 strainu: does another browser/device work?
[21:05:09] <strainu>	 Commons looks fine, I notice
[21:05:30] <Spookreeeno>	 Weird
[21:05:35] <strainu>	 Checked in FF, Opera, Chrome, all look the same
[21:05:52] <Spookreeeno>	 Commons and rowiki should be the same software wise
[21:05:57] <AntiComposite>	 I can reproduce on ro.m.wikipedia logged in and out with width > ~720px
[21:05:59] <Spookreeeno>	 It's only Tuesday
[21:06:33] <AntiComposite>	 well, partially reproduce at least
[21:07:25] <Spookreeeno>	 strainu: could some onwiki css have changed?
[21:07:38] <strainu>	 I don't see anything in recent changes
[21:07:52] <Spookreeeno>	 AntiComposite: can you trace the rule from mobile view in desktop maybe?
[21:08:01] <Spookreeeno>	 Same to strainu ^
[21:11:49] <strainu>	 Not sure what you mean Spookreeeno
[21:13:03] <AntiComposite>	 strainu, can you clarify exactly what is out of place?
[21:13:12] <AntiComposite>	 compared to what you're used to seeing
[21:15:58] <Spookreeeno>	 strainu: can you see what div id or something caused it or where onwiki the rule is being set or what actual css has changed?
[21:16:30] <strainu>	 AntiComposite there is too much width. In recent changes, the list of items only takes ~50% of the screen width, while logged off it fits the screen fully
[21:16:52] <strainu>	 And the font size is noticibly smaller, like I zoomed out
[21:19:40] <AntiComposite>	 ok, I haven't reproduced that
[21:19:58] <strainu>	 Uploaded file: https://uploads.kiwiirc.com/files/604e4de1d75caafcaf71ee800cd634f1/mobile%20issue.png
[21:20:15] <strainu>	 This is from desktop, in responsive mode
[21:20:27] <strainu>	 Left is the issue, right is how I expect it to look
[21:23:29] <strainu>	 looking at the li items, styling is the same, moving up to the divs
[21:24:59] <strainu>	 On #body-content there is an extra rule on the "bad" version:
[21:25:02] <strainu>	 .pre-content, #mw-content-text > form, .content, .content-unstyled, .post-content {
[21:25:03] <strainu>	     max-width: 993.3px;
[21:25:03] <strainu>	     margin: 0 3.35em;
[21:25:04] <strainu>	 }
[21:25:23] <strainu>	 let me try with debug on
[21:27:30] <strainu>	 The rule seem to come from https://ro.m.wikipedia.org/w/load.php?debug=1&lang=ro&modules=skins.minerva.base.styles&only=styles&skin=minerva
[21:27:37] <strainu>	 so from the skin itself?
[21:28:13] <AntiComposite>	 yeah, that is the responsive rule, it's supposed to be applied at width > 720px
[21:37:16] <strainu>	 ok, so what can I do about it? Should I log an issue?
[21:56:42] <strainu>	 I've did some more digging and it seems that for the bad page, the browser considers the box mdel as being 980px large instead of 390 for the good page. I'm simulating an iPhone 12. Still not sure how that happens or what should I do with this info
[23:56:08] <strainu>	 AntiComposite, do you have any suggestions on the path forward?
[23:56:28] <AntiComposite>	 can't hurt
[23:56:33] <AntiComposite>	 to file a phab task