I want one. Thanks.
Also, er, if you do use those and actually want better metrics and stuff, you might want to... get someone who's had less beer to... make things line up better?
Fixed for timeless in the above patch.
I'm going to be really, really optimistic for no reason.
Fri, Jul 20
General heads up for all subscribers: development of Timeless is now being funded by a Project Grant. If you're interested in receiving updates about this, I've created a newsletter about it, which should be going out ~monthly.
Thu, Jul 19
Total rejig of layout done in https://gerrit.wikimedia.org/r/#/c/mediawiki/skins/Timeless/+/446569/
Okay, mobile issue IS caused by the giant pile of indicators.
Okay, so in three-column mode you need to scroll on the sidebars. The content cannot be scrolled on. Also it scrolls horizontally really far for some reason.
Wed, Jul 18
I tried deleting the entire icons node and it didn't seem to help any. I... may have to come back to this one later.
...what is going on, indeed. I can't even get to the content on desktop in chrome... there's just this giant empty space off to the side, and all the content itself is just... gone.
So what have been all the versions and what are y'all really after, here?
As a wordmark, that version's pretty good.
Okay, question - in a way, does this sort of just depend on making a new mw logo that meets requirements, such that then parsoid can have an appropriate derivative logo that is actually usable in print etc?
So, uh, what should it look like? Wikibase logo modified how? What's a registry? What is this thing? What does it do? What do you associate with it? Bees?
SHITTY LOGO COMING UP.
Sun, Jul 8
NOPE, STILL HAPPENING. Or again. Or something.
Sat, Jul 7
Awesome. Let's consolidate the non-sidebar stuff! A probably header one, a probably footer one, anything else? I'm thinking those two will be the most common - header for global stuff, footer for, well, extra footer stuff. Possibly also global, but we don't actually care HOW folks use them as long as it serves the likely cases in some way...?
I feel like that last paragraph should be a bug all on its own.
New idea: consistentify HasSomeColours/Splash/etc global project navigation into a general cross-skin thing they all pull on to render, use same approach here.
Leaving the Timeless project on this for tracking, since while it's not specific to Timeless, it does affect it.
Apparently not really a problem with timeless; the echo notification number colours were only implemented for monobook/vector and simply do not appear in any other skins.
At this point the skin's been there long enough that it's basically it by default. Chuck spec, but still need to add some colours...
...may also want to add a config variable so third party sites can just throw in their sidebar instead of having an entirely separate menu.
I recommend looking into what BlueSky does, both for icons and customisability. Essentially you probably want to create a second navigation interface message structured like the sidebar with an extra |item for icon specifying, with a parser that functions similarly to a simplified version of the sidebar parser that outputs a standard portlet/set of portlets. This approach allows for onwiki customisation both for the rendered html (editing the mediawiki namespace interface message) and js overrides using the standard addportletlink etc functions, which work with pretty much anything following the expected structure.
I started my browser and most of my phabricator tabs turned into complaints about too many concurrent connections. Is this the same thing?
Sun, Jun 24
Based on what we discussed, is it actually possible to do it without js currently?
Off the top of my head the only reason I can think of why they'd be sorted alphabetically to begin with (because as you say, the on-page order is indeed more logical) is probably because they're actually being pulled straight from the database or something similarly idiotic because there's just no built-in way to get them... not entirely pre-rendered as html? Even so, if it normally gets them in the proper order, there must be some way to replicate the behaviour...
Jun 17 2018
Also the content fonts are dumb.
Other issue: using serifs for all can be a bit jarring for users if they are used to vector, as that only uses serifs on headers with an underline.
- add underline to h3, but smaller than h2/h1
- lose serifs for h3-h6 or h4-h6
May also want to check all the other skins in gerrit...
Jun 16 2018
What's the difference between expected and actual behaviour, again?
Current tabs layout also just kind of messy in general, according to users. Perhaps in order to re-evaluate design in general?
Jun 15 2018
If you are so eager to have this feature that after the first rushed deployment you do another one without proper investigation of all issues, waiting for the translation, and proper communication of the opt-out setting, so be it. That's not what I think of as good practice in our volunteer-driven ecosystem.
Thanks. I'll have to try something else for this one.
So... yeah. Let's go with fixed.
I thiiink the other issue was resolved upstream, and somewhere at the same time the same effect that the patch fixes moves in to replace it?! I don't even know.
Jun 13 2018
Can someone check if this is still happening, with and without the above patch? May have been resolved upstream regardless.
General note that the above patch is actually resolving something totally different from the original problem that was causing this, but that may have been fixed upstream regardless. Or something.
Does this conflict with an already extant solution I don't know about? (Pleasesayyespleasesayyespleasesayyes...)
...wasn't page previews set like that because it'd conflict with the power user gadgets that also include the same functionality, along with a lot more? Or am I thinking of something else?