My comment from an ephemeral chat client :)

I honestly don't off hand know of a lot of other structures like this one.

rMW resources/src/jquery/ has the source.

Never mind little ol me then

In T271588#6733143, @Tgr wrote:

Yeah, TemplateStyles forces selecting something inside the parser output, not the parser output wrapper itself. Changing that doesn't seem dangerous

Yeah, doesn't seem dangerous to me. I can't think of any particular abuse that you could do with the wrapper that you couldn't already do outside it, seeing as it's not the scaffolding or anything on the page structure.

In T271473#6731938, @PrimeHunter wrote:

Also discussed at https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Problems_with_Tables_and_Infoboxes

Something in Timeless is adding style="width: 956px;" to <caption>...</caption>. The number 956 depends on the window width. It apparently tries to center the caption in the whole window instead of the table.

For some reason, the normalize styles are being loaded/appended to the main Monobook styles.

Made a workboard for protection project and moved the last open task there.

I moved the table issue to T271473: Timeless userboxes fail to float right and take up large page space.

Since it's convenient, let me just merge my comment from the other task here.

If we really think there is a need to track these otherwise, a "(New) Properties Backlog" column on css-sanitizer would also do.

I honestly don't think this task is needed for the purposes of tracking. There are only a dozen tasks in css-sanitizer and its job should almost exclusively be "add new CSS support" given the fairly successful rollout of the primary-using extension, which is TemplateStyles. All the tasks tracked by this one are also in this project. I do think one or two could maybe stand to have a few other projects. I almost feel like css-sanitizer should be a subproject of TemplateStyles; is it used elsewhere (should it be?)?

Pointed to en.wp Help:Search which indicates that insource without regex search is whole word only.

In T271053#6717466, @Xaosflux wrote:

@Izno the UI control is the universal stop button on "Live updates" with a tool tip "Turn off live updates" - however, it isn't really stopping or turning off the live client-side processing.

(Exciting!)

I'm not sure about that rename @Xaosflux . It is pretty apparent to me that the requests go out because non-live update wants to be seen as being responsive to new changes (so that "You have new changes" occurs almost as soon as you actually have new changes).

I believe the upstream is https://bugs.chromium.org/p/chromium/issues/detail?id=1159852 , which looks like it will be fixed for most Chromium users soon.

I'm quite happy with the Firefox native MathML rendering. :3

(Coincidentally pictured, there is something wrong with the bar graph display only for recent months.)

Since this is the remaining open task for REVISIONID for preview indicator things, I'm just going to leave a note here that I closed T53660: Detect the edit state for modules which help users and helpers invalid, which has been open some time. Not entirely sure that was the best thing to do, but it seems like it.

I'm going to close this invalid. Detecting whether a page is being previewed, the sensible case for this, is already supported in wikitext and in Lua. If you need the exact syntax for Lua, see https://en.wikipedia.org/wiki/Template:If_preview or search for REVISIONID in module namespace (I do not know the wikitext version offhand). My understanding is that this method of detecting preview is supported and will continue to be supported.

Besides the use cases outlined in T137900 that probably inspired the "give a better warning system" naming of this task, I thought of another: several templates emit the user name / timestamp as an indicator of who last touched a particular page and when that page was touched. I believe this is done to help identify whether a page may have been maliciously touched, or whether the author particularly has been active on a page.

In T200206#4505041, @Krinkle wrote:

In T200206#4504920, @Anomie wrote:

[...] or you could change the style rule to .navbox + link + .navbox.

This might be a use case for the general sibling combinator, which would look like .navbox ~ .navbox.

What is the specific issue you are identifying with this citation? Is it:

For reference, we're now categorizing a few different titles that clearly indicate an issue in CS1 errors: generic title, one of which is Bloomberg. The patterns checked are in CS1 configuration as:

(The message box module and templates are due for an upgrade from 10 years ago when they were designed, it's just a rather complex design.)

In T104770#6681109, @cscott wrote:

I think <aside> like <section> is arguably part of the skin / meta-layout, not part of the article content.

I don't see it. I have real use cases that meet the description of aside. Why should I be barred from its use? :)

No fundamental issue from me, I was just the first to catch the original description before work started. :^)

Given there's a large active community discussion about this problem on wiki as Kaldari pointed to, it might be a good idea not to fork the discussion.

pull quotes or sidebars, ... for groups of nav elements