[00:03:26] it's not old vector [00:03:35] but it's different [00:03:40] and im confused [00:17:07] Is anyone else getting 502/503 errors? I wasn't until a couple minutes ago but suddenly am [00:17:34] i'm also getting those consistently [00:17:53] now it's loading [00:18:00] yeah just started up again [00:18:13] weird hiccup I guess! [00:25:34] yeah, i got them for a bit. it happens sometimes, but seems to be ok now. [00:28:26] Does Miraheze have the parser functions extension? [00:29:20] Yes. [00:45:18] The first one is definitely old vector [00:45:29] Notice how the second image says switch to old look [00:47:48] global preferences probably [00:51:39] then why is the old vector navigation on vector2022 [01:08:20] what [01:08:26] its just the same navigation [01:08:35] it just looks different on both skins [01:28:40] old vector navigation includes design [01:29:01] mentioning it without any details doesn't automatically make me not mention them [02:42:24] What.. [02:44:32] First screenshot old vector, second screenshot vector 2022 [02:44:58] the old navigation [02:45:05] is on the new [02:45:41] That’s not the old… [02:45:47] Dear lord [02:46:10] Custom CSS exists [02:46:27] How? [02:46:39] ahh add topic [02:46:41] okay okay [02:46:56] add ?useskin=vector2022 to the end of the url, it won’t change [02:47:09] Then add ?useskin=vector to the end of the url it will [02:47:32] Ive been using old vector since 2014 I know the differences [02:48:54] That is definitely new vector with CSS changes [02:51:31] it's not [02:51:59] We’ll just agree to disagree [02:52:04] uh [02:52:07] you're wrong [02:52:09] and im right [02:52:16] ^ [02:52:18] No. [02:52:26] This is a battle that will lead on for years. [02:52:30] But you won't know it. [02:52:43] No it won’t, I’m to mature for that [02:53:09] ^ [02:53:24] Ok [02:53:29] Have a great day [02:56:28] Stuck on captcha. [02:57:47] @orduin any idea when captchas will work again [03:39:13] Is it possible to implement a custom font using css? And if so, what's the code for it? I already have the ttf url [04:07:21] We only allow URLs in our CSP whitelist [10:35:54] Could you maybe screenshot your pages? Show exactly what you click? [10:37:06] also- please does anyone know how to keep my images from getting all stretched [14:06:58] it helps if you share a link or screenshot, otherwise it can be very hard to figure out what the problem is :) [15:31:51] It's when I look at images that are on a page- not every image, just a couple of them. For example, on Mortimus' page (https://decapedia.miraheze.org/wiki/Mortimus), it gets stretched out like above (the one with two of the same guy facing each other). [15:38:04] what the [15:38:39] when i click on it though, it's fine [15:41:36] [1/2] yh i know about the resolution- I thought that might just be my wifi [15:41:36] [2/2] Is that smth that can be fixed too? [15:41:45] Well, I'm glad that it looks normal to other peopleQ [15:41:54] Thanks! [15:47:53] this doesn't though [15:47:58] on the page it's like this for some reason [16:12:32] <34.29cm, replying to mx.lilasekhmet> It looks normal, with regular resolution and no stretching when I click the link [16:13:34] <34.29cm> what's weird is that when opening it, this shows up for one second before the page loads...? [16:15:19] <34.29cm> I really like the accessibility options on the left though! How does one do that? :O [16:33:10] Looks like the css didn’t load yet [16:35:32] <34.29cm> Yeah, but it happens systematically when opening/refreshing this Wiki, which I haven't seen happen on other Wikis :x so I don't know what's causing it, but maybe the user asking already knows about this [16:51:02] Happens for me too, probably that evelution skin is just very heavy/badly optimised so it takes longer than normal to load (there doesn't seem to be any signifcant extra css or js on neither common or evelution css and js pages, so must be the base skin itself doing it) [16:54:10] and those "accessibility options on the left" I suspect to be at least part of the option, being able to swap between them on the fly like that... yeah that means every single combination of those have to be loaded each time you load a new page [18:10:13] Is it possible to make the tops of tables sort of “lock” and not go off screen until you scroll past the entire table? [18:23:33] Is there a way to remove or place elsewhere the text link for the Changes Page? Or alternatively make it so that the page title doesn't take more than 1 line? [19:40:57] How do I change my entire wiki's main text color to white? [19:52:03] Why does this not work in changing the text color [19:52:37] @zppix https://meta.miraheze.org/wiki/Special:Contributions/78.211.76.139 looks like more ban evasion [20:15:47] css selectors depends on your skin etc, so you should link your wiki [20:16:36] use the `/auth` command to be able to send links [20:29:03] [1/12] I suggest this or hiding the last-edit indicator (this info is on the bottom of the page also) [20:29:03] [2/12] `#firstHeading { [20:29:03] [3/12] clear: right; [20:29:03] [4/12] } [20:29:04] [5/12] .mw-indicators { [20:29:04] [6/12] font-size: small; [20:29:04] [7/12] }` [20:29:05] [8/12] or just [20:29:05] [9/12] `.mw-indicators { [20:29:05] [10/12] display: none; [20:29:06] [11/12] }` [20:29:06] [12/12] should put it into MediaWiki:Mobile.css since it's mobile specific [21:40:10] idk, I just use the eevelution skin and I think that just does it automatically. Or maybe it's one of those function thingies, like, the boxes you check in the wiki settings? [23:10:44] I’m on monobook.css does this not work on that skin? [23:21:10] really can't tell just from that since I don't use that skin <:ThinkerMH:912930078646730792> [23:22:48] you can try slapping on !important after the white, like `white !important;` [23:29:11] Aye, that worked! [23:29:16] Thanks