I'll be honest, I'm seriously considering abandoning the infinite recursive embedding support idea, and this saddens me greatly.
Oh, it was here! I appreciate the nagging, too, since I'd kind of lost track of this in everything else.
Sun, May 19
Still have json editing mode available, if they want. Just add a new tab for that one.
So it just dumps out the header, then dumps the content of the thiccness pages on the page.
Sat, May 18
And each thread is just a separate page. Somewhere. Where?
So, uh, add new content model for managing threads, I guess?
Schema basically goes:
Because you can only have one slot of a type per page!
NOPE THAT WON'T WORK.
Fri, May 17
Okay, we are going to do this using slots. It is decided.
Tue, May 14
Really need to do T223186 so I can find the others...
Current example: https://test.wikipedia.org/wiki/Wikipedia:WikiProject_Test
The above did not work. See: https://test.wikipedia.org/wiki/Wikipedia:WikiProject_Test/Page_list?useskin=monobook
Also I'm kidding I love you guys.
In contrast to the other skins, Timeless sets border-collapse: collapse and border-spacing: 0 to all tables, including all tables in the content area. The issue can be fixed by just removing these two properties, or making their selector more specific so it does not cover inboxes and such.
Okay fine I hate you all I'll fix this.
I meant to bring this up before, but I guess I forgot - I'm thinking a whitelist probably would make more sense in the meantime. We know what skins have this thing, it's not particularly likely new ones will add it unless something major changes with the development/usage of this or related extensions, and it appears there is a fallback behaviour for those that don't have the better thing, so we should be falling back to that by default, instead of unlisted unsupporting skins just winding up with nothing at all.
Need to perhaps rethink use of languages in general here.
But if this doesn't do what you wanted, please do say so.
@ashley evidently resolved this by removing the legacy hook in question entirely.
So what he said.
Should probably just put the single default icon next to both options, and kill the silly new one.
One of the recent forms patches where I messed up the fonts should have fixed this (probably https://gerrit.wikimedia.org/r/c/mediawiki/skins/Timeless/+/504963). h4-6 are all fairly similar now, but honestly that's not unusual...
I'm going to close this until someone complains again.
You know what, this is a terrible idea. It's there as an option regardless...
Do you have any examples to test against?
Based on randomly guessing, there's a very good chance that the actual issue behind T222670 will also make this rather difficult.
No longer seeing this? I dunno.