@kchapman Would it be possible to do this meeting at some other time/day? As one of the people most familiar with the current skinning system, it'd probably be good if I could make it, and that is not a time I will be able to make as I am going to be on a plane somewhere over the atlantic.
Tue, Mar 12
All right, then.
Do you have any thoughts on T217158?
Mon, Mar 11
Should just be deployment lag. If it's still broken after thursday, please let us know.
Perhaps it is indeed time to move onto the truly insane 'implement iframes in flexbox' idea...
I have tried everything. This is me screaming in my corner because even the things that seem to work inevitably quit working anyway in a week or two.
Soooo... there actually was some sort of consensus at the time, right? I'm not actually expected to get an undefined new consensus to override something unspecified, am I?
Sun, Mar 10
You know, that is a good point about Wiktionaries being their own thing. I'd personally still prefer to see this discussed across the lot of them, but... maybe I'm also partly just saying that because I'm trying to put the whole thing off because this just scares me, too. Changing skins is a big thing, and we definitely need to be working on actually moving toward doing that, on all projects, never even mind if it's to the same skins, but are we ready? Is this skin ready?
Fri, Mar 8
I've just been avoiding this entire thing because it scares me (sorry), but if we do such a change, we do probably want to do it across all (normal) projects, and have a consensus that it's time to change the overall identity of the lot, since visual identity is a huge thing.
Thu, Mar 7
Fri, Mar 1
Wed, Feb 27
Thu, Feb 21
Or, hells, any more specific suggestions how to look into the feasibility of getting such a consensus now, or where I ought to inquire further on the topic, would also be much appreciated.
Filed T216703 about MonoBook specifically.
Do you have any links to this? So far I've really only seen people be confused by the inconsistencies, but that would have all been after the change, obviously.
Feb 20 2019
Forms to check:
i r stupid
Apparently some similar issues on createhubfeature.
For mobile particularly, we really need some sort of indicator like that. Unfortunately there really isn't any way to do that without putting in either some rather complicated extension-specific stuff in the skin, or skin-specific stuff in the extension.
Feb 19 2019
So its expected there would be two types of skin variants (themes): ...
Perhaps some history of how skins are will help clarify things here:
Feb 18 2019
Feb 17 2019
Feb 15 2019
(The issue is the space for the username is very small currently and it just replaces it with 'account' if it doesn't fit, which... isn't really ideal. Need better handling in general, as this use case means it'd be likely to be even longer.)
Okay, I gotta figure out how to make the header in general less feckin' dumb in the first place to make this actually likely to... show up, and such, but that sounds good to me. Suppose there's no particular reason not to just do it as is in the meantime, regardless...
The meaning of such a highlight is going to be very unclear by itself, as the meaning it's supposed to be conveying depends on the user having prior knowledge of the context.
Timeless doesn't 'expect' echo; it uses the usual in-content banner without it.
Feb 13 2019
Filed T216046 about it being generally suboptimal.
Hmm, looks like whoever said the yellow thing was a gadget in general was also wrong on that one. It is hardcoded into the extension, which, given that it only even makes any sense on skins with a string-layout like monobook, seems like a rather bad move given how uncommon that actually is these days.
Dammit, you're right, the colours aren't working again, unless I dreamt that they were in the first place. It was such a hopeful dream, too...
Feb 12 2019
Okay, thank you, that makes me feel so much better about all this. Cool!
I was under the impression that the entire point of the right was for countering vandals and spammers. It sounds like maybe these two wikis should perhaps considering changing that configuration, if it's a problem, as well?
Or is this a particular issue with specific devices, such as on mobile? Because if it's a lot easier to accidentally click on it on a phone, having a confirmation specifically on those devices could make a lot more sense (so perhaps as a part of MF?).
Is this actually desired? I know some wikis have scripts to do this sort of thing, but scripts sound exactly the place for it in the first place - for the most part, the relevant problems we have onwiki are with insufficient tools to counter vandals and spammers, not that they're too powerful.
So the expectation is that the username be pulled from the data array, so that way your extension can just change the display name to something else?
Feb 11 2019
The reason for the border collapse was to get 1px borders between the cells instead of 2px, but evidently the default wikitable styles don't need that, which is interesting...
In Timeless, the assumption is that with Echo/Notifications installed, the coloured notification badges should be sufficient indicator on their own (and the colours should actually be working now, too). This is why the badges are explicitly moved out of the main menu, and in terms of skin-extension interaction, this handling is consistent with the general intent of Echo/Notifications itself.
Feb 8 2019
The links are kind of important.
Feb 7 2019
Basically this RfC is really just us asking if there's any particular reason not to merge the associated patch, once fully tested and such, because it's slightly larger than the usual change.
Perhaps this better explains what we actually want to do here? I don't even know how to properly explain any of this anymore.
What in tarnation...
You know what, I think I did this at some point.
Feb 5 2019
Jan 29 2019
I love you.
Jan 23 2019
There may be use cases outside of skins - are any other functions here often used for other things?
Jan 18 2019
It's BAAAAAACK. And possibly wasn't even entirely resolved to begin with this time either. Something about it only working the first time, and then any subsequent anchor would wind up positioned wrong anyway.
Jan 17 2019
Any special specialpage made for this needs a longer name.
Just using changecontentmodel technically works (so fine for handling), but then you just wind up with the json content... in a wikitext page.
Just disabling it without doing any of that results in this: