It would be good to list out the ad hoc actual implementations of internationalization/localization.

At first glance, it looks like Parsoid/PHP matches legacy parser rendering here.

Might want to consider opening a new task or tweaking this one for all work arounds for PHP < 7 since all supported versions now require at least 7.0.

I don't see the issue any more for some reason. Maybe it was upstream or maybe it was Firefox or the gremlines or... 😃 .

The revision slider has a pin today. In Timeless today (which since the last release is now displaying some weird offsets), those look like:

The Syrian civil war template is a known issue on wiki even with legacy parser. We've had to remove details at least once from the template before.

I see a TOC for enwiki with links that work but no headers, in multiple skins. The source also does not have the headers.

In T235459#5573946, @Masumrezarock100 wrote:

Yeah, because it is Timeless. It is a responsive skin for both mobile and desktop. Are you saying that it should look same?

In T234090#5571471, @Tgr wrote:

The one topic I'm missing a bit is how to get more involved in global standardization efforts (such as W3C).

Is this T150418: References pasted from read mode should be dropped until we can support them properly actually?

Per Volker's comment at VPT, this was fixed as a result of T234510.

The original reporter was using Chrome.

There's a lot of stuff in https://lists.wikimedia.org/pipermail/foundation-l/2010-May/thread.html from what looks to have been a significant discussion on the topic. General tone seemed to be "nope, we're not interested in categorizing content directly for the purposes of censorship/content filtering".

So, the ICRA hasn't existed in nearly a decade and the PICS is also no longer a thing, though its successor POWDER appears still to be an active W3C set of standards... of approximately the same usefulness as generically describing the images in RDF (since it is not obvious to me that any vendors have implemented to the use cases described by that standard), which is what StructuredDataOnCommons is going to do for files.

I added T234733: User field in OOUI Special:Contributions is very short as a post-rollout subtask.

This looks to have been resolved @Legoktm @Volker_E ?

Syntax for attributes is something I made a task for at T202083: First-class wikitext support for ordered list item value which I closed duplicate of the problem I was looking to solve in that context. General gist I suggested was similar to the table syntax, namely: # id=A class=X | BCD where BCD is the list item content. I can see users going for that syntax. I don't really understand the proposed "table" syntax above (:::|id=foo|class=bar| ("like table syntax")) since that's not how table syntax works. "like", but definitely not.

I agree entirely with Anomie in T230683#5434186. His shot at a mockup is a bit reddit-ish too, which seems to be accepted elsewhere....

Some thoughts, some of which are in the gist of the above discussion and some of which are new points.

Might be nice to have a pin on the article history page as well. (I don't know, just making a comment that I doubt anyone would be bothered with consistency there.)

Not sure this should be closed; the bug in the description is not mine nor was my fix going to resolve the above.

In T234030#5534080, @DCDuring wrote:

The 'example rendering' above shows each reference taking up a line of screen space, though containing just a few characters. Can't we make better use of vertical screen space by lining up the page references horizontally?

In T234030#5534069, @awight wrote:

In T234030#5534033, @Lucas_Werkmeister_WMDE wrote:

Will it be possible to name and reuse refined references?

Good point! Yes, I think that should be possible to reuse a sub-reference. We won't support a second level of nesting, on the other hand. No "refines" of a refinement, just because it would increase the complexity of the UI and rendering, for little gain.

In T120085#5517353, @Krinkle wrote:

This is still an open RFC. [snip]

This one will probably require a user notice before WMF rollout and maybe even a "do you guys want us to do this" question to the communities.

You shouldn't be opening any pages in a new tab in the general case. See https://www.w3.org/TR/WCAG20-TECHS/G200.html

This is T185840 and I will be closing accordingly.

Possibly this discussion also demonstrating the issue.

In T232491#5481717, @BBlack wrote:

Can any previous reporters confirm the same continued breakage, or new success?

I have issues saving in Chrome (Win10) on my work computer but no issue at home on Firefox (Win10). I use WTE2017.

In T232293#5473752, @SerDIDG wrote:

@Izno, please check one more time, where nowrap class is implemented: <nowrap>date</nowrap><footnotes> <nowrap>age</nowrap>. Normal space character separates these two pieces and should wrap.

Some of us use VE. Did you check in VE also?

Module:Infocards sets class=nowrap on that element, which has whitespace: nowrap from common.css. The elements are not wrapping accordingly.

Minor note, there is a duplicate listed dependency at 1702 and 1705 of Resources.php.

Discussions closed; dead-url deprecation remains.

@Isarra You might want to put the word back in wide mode.