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.
Thu, Sep 19
You shouldn't be opening any pages in a new tab. See https://www.w3.org/TR/WCAG20-TECHS/G200.html
Sun, Sep 15
This is T185840 and I will be closing accordingly.
Sat, Sep 14
Possibly this discussion also demonstrating the issue.
Wed, Sep 11
Tue, Sep 10
I have issues saving in Chrome (Win10) on my work computer but no issue at home on Firefox (Win10). I use WTE2017.
Mon, Sep 9
Some of us use VE. Did you check in VE also?
Sat, Sep 7
Minor note, there is a duplicate listed dependency at 1702 and 1705 of Resources.php.
Discussions closed; dead-url deprecation remains.
Tue, Sep 3
@Isarra You might want to put the word back in wide mode.
Mon, Sep 2
Sun, Sep 1
Fri, Aug 30
This is gadget worthy IMO, not skin worthy. No other skin has it today.
Wed, Aug 28
I'd be happy today if I knew what to reset in user CSS for the 'everywhere' option. I have a 1200px res or so, so nothing super high-def (which is the problem case when you start looking at removing the max width). I don't know about other people.
Mon, Aug 26
On an aside, I don't entirely understand why mw-datatable and wikitable are two separate sets of styling. :^)
Why would VE be designed to duplicate the skin CSS? Questions that keep me awake at night.
Sun, Aug 25
Aug 20 2019
Aug 11 2019
Woops, this was a false alarm for me (in the sense that my bug I do not think is this bug's bug). The template in question is outputting an empty div (besides some inner elements, which themselves contain no content) that Edge/IE treat as an interesting div and consequently assigning that div height. It doesn't seem to be an issue if the div gets some css (display none or float right).
Aug 10 2019
Anomie pointed me here from this en.wp topic. I think this one might be the bug causing the issue described there. It affects IE11 as well, though I haven't personally tested that case. However, I tried to set display: none in that case and what I got was the li bullet styles disappearing in Edge instead of the link element.
Aug 9 2019
TemplateStyles cannot fix reasonably the case of substed templates.
Clearing Mobile.css of TemplateStyles requires the same level of effort as cleaning Common.css, more-or-less. As I've described elsewhere and multiple times over, there are multiple cases (hlist, navbox, infobox classes as examples) where classes are being defined in-page, not in a template, nor remotely near any template, and relying on Common.css to provide the related CSS.
I'd rather just see TEs get editcontentmodel tbh.
Aug 5 2019
In recent Chrome and Firefox, cannot reproduce the beginning of the chain as I laid out in the original task actually. Trying your way, I cannot reproduce this issue either. I'd put this down to browser version or fixed elsewhere since.
Aug 4 2019
On an aside, this request was also made on T155813: Decide on storage and delivery method for TemplateStyles CSS (there may be other discussion related in that task; I just happened to be reading it because of the discussion about TemplateStyling Template:Documentation):
Jul 31 2019
I am not sure what you're asking there.
Jul 28 2019
T173531: New 'edit source' icon may also be of interest.
Not really? The Minerva icon for edit is a pen; the Minerva icon for view
source is a pen with a lock in the top right.
May also be another issue with T181184.
I've been musing on this problem and I think it's due to some default of some sort on padding, or possibly that the default column width in Timeless doesn't match that of Vector. If I zoom out from 100% just once with the default widths of a responsive reference list on en.WP, the columns become obvious, so it's clear to me the list is getting the columns styling.
One of the bigger issues is that the table headers have no borders for me at least. This is probably bad for poor-sighted users, who need the strucutre of obvious cells.
Jul 22 2019
As for performance gains/losses, that doesn't seem like a good criterion.
In general, I think we should work to get as much out as possible so that
it is obvious to (re)users where our CSS lives. The difficulty is in the
styles that are widespread and not necessarily confined to one template.
Also add the styles to a module subpage if they are invoked from a module.
Jul 17 2019
Jul 10 2019
Today (it's a bug), if you want to view a page without TemplateStyles, preview the page using VisualEditor.
Jul 9 2019
Jul 8 2019
On the point of unified diffs, WikEdDiff provides unified view and I almost exclusively read diffs using it rather than 2 column.
Jul 7 2019
Jun 26 2019
Jun 24 2019
Jun 22 2019
YYYY-MM is generally insufficient to distinguish from a year range. I think there has been discussion about that particular amount of information on Phab, but it's a regular discussion topic on en.WP.
Jun 10 2019
Jun 9 2019
Jun 6 2019
This is not a problem with the software. You need to fix Template:Citation/core. You should probably leave a note on the talk page there.
Jun 1 2019
And new permitted values.
May 31 2019
The page had local interwikis defined. I removed them.
May 30 2019
May 27 2019
May 25 2019
T157670: Changes to MediaWiki code related to parsing can leave links tables out of date and/or T221795: Refactor Category::refreshCounts logic to a job and simplify are I think the ones of interest? Just merged this to one in fact based on a similar merge that Krinkle did.