Wed, Jan 17
If we want to propose specific projects for this, should we just do the usual discussion on-wiki to see if there's consensus, as it looks like svwiki has already done? Is there anything in particular people should know when discussing it? What would the timeframe look like to editors?
So when's this happening? Wheeeeeen?
Has nothing to do with hardware acceleration; still occurs with it enabled.
Sun, Jan 14
That patch does seem to mess up ULS's handling (forced visibility) of empty languages blocks. I'm not sure what to make of it, though, so whatever.
Sorry, I was on the wrong computer for awhile there and it kind of got lost in backlog.
Sun, Dec 31
Start with that, reposition, replace icon?
Fri, Dec 29
Yeah, I've been meaning to come back to this when my brain is actually working, but it hasn't happened for whatever reason. I've asked @ashley to take a look in the meantime, though - if everything's sane he can totally merge it anyway. >.>
Thu, Dec 28
@grey-bright is what is used for image borders in thumbs. It should be the same. Whether or not the value is too light in general is a separate issue; you are welcome to file a task about that as well.
Wed, Dec 27
@Od1n: Use the @grey-bright variable.
This has nothing to do with SWAP. Probably caused by disabling hardware acceleration combined with some css chromium doesn't handle well?
Fri, Dec 22
Typically for images on the page, we don't want the text to wrap around them on mobile. This specifically applies to thumbs, which are floated left or right, usually, in the content.
Dec 21 2017
Great idea. If anyone wants to make a patch for that, please just yell at me and I'll merge it.
Dec 20 2017
Since we actually have a more thorough style guide now.
Dec 19 2017
Oh, also hardware acceleration is disabled, may or may not be related, but now we're getting into the general rabbit hole of chromium's utter instability.
Er, this is on linux (mouse clipboard), Chromium 63.0.3239.84, and when running out of SWAP. Yes, SWAP can be slow, but not this slow, and not for this, as evidenced by other skins not being affected. Tested on meta.
Dec 16 2017
Okay, sometimes the tools one is also behind it? I don't even know.
Search suggestions cover up the search in ancient safari on ancient iphone.
Dec 14 2017
Dec 10 2017
There is also the very obvious question of do I even care.
It was some sort of fancy api thing to get the information and completely reimplement the toggle ui. Or possibly even more than that. @ashley?
Dec 9 2017
Okay, this is happening in every skin with css hover dropdowns (splash, vector, bluesky, etc - not greystuff because that one is actually js). Appears to just be a chromium bug.
Dec 8 2017
Nevermind, I think I found a new browser.
Since this being gone means I can't use oldopera for css editing anymore, does anyone know of any extensions for chrome to bring back oldopera-style css editing in the developer tools?
That preference isn't exactly new, though.
Dec 7 2017
The 'approximately' was a joke. Because it was exact... and generally, exactly wrong.
Dec 5 2017
(The issue does not occur on mobile resolutions without going through MF. See: https://en.wikipedia.org/wiki/Yellowhammer?useskin=timeless which does not have the ToC issue, but also lacks all the other MF content improvements.)
Thank you, looks like it's a compatibility issue with mobilefrontend.
What project is this on?
Dec 4 2017
Sitenotice shows up fine for me on testwiki. https://test.wikipedia.org/wiki/Main_Page?useskin=timeless
Dec 2 2017
Huh, okay. Support clearly needs to be added.
Dec 1 2017
How ballpark is ballpark?
Can we also only look at logged-in users? This being about user preferences, and all.
Can we make this just content pages?
Yeah, I'd love to have this now that Timeless has had a chance to stew everywhere for a bit. Be good to have an idea where we're starting from.
Thanks. Looks like that can happen in all skins, though, so I'm not really sure how to avoid it besides maybe using custom fonts...
Nov 30 2017
Nov 29 2017
I mean, I kind of want to replace the entire text with something... shorter and less silly? But in the meantime, that is totally reasonable. Or stuff.
Nov 28 2017
Minerva should reuse the same footer links that all the other skins do instead of implementing this specifically.
@Menthe I fully agree; the right sidebar isn't going anywhere at high-resolution because there's just no good reason not to use that space (and it's already collapsed into the left at lower ones so the content doesn't get too squished). And moving the infobox into it is an excellent idea currently blocked by the fact that infoboxes are just content and it's hard to make a skin handle specific content, BUT that is definitely a very important use case for actually making that into an extension so we can do that. Apparently there's an RfC and stuff already, but I don't remember where.
In which part of the interface is this coming up?
Nov 27 2017
I mean, I'm sold. overflow: hidden sounds good to me.
No, we should totally tell the wikipedias to do that. :D
Overflow:hidden results in the overflowing content being just... gone, though. Which means if you have a too-big table, it can't even be accessed.
Nov 25 2017
catlinks mw-normal-catlinks mw-hidden-catlinks
catlinks-sidebar p-catlist-normal p-catlist-hidden
The issue here is that Timeless' unique approach to category handling (the sidebar stuff) does not follow the expected format/pattern of category handling elsewhere. (Specifically the normal approach is a core function that just generates and inline list, with consistent ids and all that, whereas Timeless reimplements its own handling in order to format them in the sidebar, and possibly even sort them better? I don't entirely recall the specifics, but it's likely not using the same ids and stuff, either.)
I don't really want to use the offered line because it's so specific and infoboxes are on-wiki-defined stuff and they could be anything in practice, but I also can't think of any other solution that would actually work as-is besides just specifically overriding it for every template/whatever that needs it.
Actual report from #wikimedia-dev:
Nov 24 2017
Is there one for generic iOS, too? Both would be good.
Nov 23 2017
These were all supposed to have different things in them - some desktop features, the mobile interface, etc, but I guess I haven't actually implemented any yet, so it's a bit silly currently... er.
Which wiki is this on?
This is only happening in special:contributions? Not anywhere else?
Okay, why did I make a new one?
Nov 22 2017
...huh. How was it added? Gadget?
Naw, 'wrong colour' was just that it doesn't match the colour scheme of timeless (different red, different blue/grey/whatever it all has). This is it not even using the right kind of colour. If the colours flat out aren't happening, this is an actual functionality bug, as opposed to me just griping as a designer.
Nov 21 2017
Nov 17 2017
Yeah, we should really either deploy it to all the remaining ones with specific consensus soon and then follow up with the rest, or just... do them all and be done with it. These waits have probably seemed completely ridiculous to the actual users, and the worst that's happened anywhere so far seems to be header overflows, which just mean Timeless itself looks stupid.
Nov 8 2017
Oct 17 2017
I submitted another grant proposal regarding getting financial support for Timeless: https://meta.wikimedia.org/wiki/Grants_talk:Project/Isarra/Post-deployment_support
Whenever the window for those wikis winds up being, could someone give me a heads up beforehand so I can be sure to be around to fix stuff? (Note: I'm back in the US now, and only awake this week between 15:30 and 3:30 UTC and I make no guarantees about being coherent or understanding a thing about what's going on even during those hours because I'm still apparently sick, but if stuff happens before then, I can also just deal with it once up, or stuff. If you don't actually need me around, that's great too. Thank you for bearing with me. I would like to stop being sick now.)
Oct 16 2017
Sep 26 2017
If you need me around, I recommend anything that's not US evening. Or next monday/tuesday. Other than that I'm not sure it matters too much.
Sep 12 2017
Yeah, it should appear where the edit link usually does. This is bug.
Aug 28 2017
But I don't want it to get lost, either.
Reopening because there's a bunch of new stuff on this and I don't have time to deal with it all right now.
Aug 25 2017
Unfortunately it might take awhile for me to sort this out, though. Need to actually find an IE10 somewhere, and such. (Maybe one of my vms has it, but this machine isn't even set up for that anymore.)
Wow. That's some impressive not playing nice, there.
Let's rip off bluesky (owl (wikihow))! :D