Sigh. Never mind, I need to learn to spell an end tag.

In T217944#8034801, @Dinoguy1000 wrote:

@Izno Do you have any examples offhand? I tried looking earlier, and again just now, and couldn't find anything (other than how some people insist on using backticks for opening quotes). The only thing I can think of, and can find, is the grave accent, which the backtick is descended from but semantically distinct and encoded separately from; I don't think grave accents ever appear except as diacritics on letters, but could be wrong.

In T308396#8045720, @Aklapper wrote:

@Izno: Maybe worth a separate ticket to request a v4 release (to be listed on https://gerrit.wikimedia.org/g/css-sanitizer/ )?

In T311381#8032151, @Nikki wrote:

I don't understand how something not being needed for the majority of users means we should be prevented from including it.

I think there are too many languages where a single backtick is going to cause issues. Double backticks might be feasible.

... JJMC beat me to this comment while I was writing it:

This script constitutes a privacy violation for anyone using it, and any choice to make it a gadget on Wikidata should make that very clear in the gadget description.

In T311321#8026447, @freephile wrote:

...

This isn't a bug but instead two different operating systems and/or font stacks selecting a different appearance: both appearances are valid. I don't think there's anything to be done here, but you could sell me on this being a task to reduce the available font sets in an attempt to make it consistent.

That would make sense.

Will need to special case <link> as well.

This is explicitly not implemented. Search support means Special:Search.

In T226797#8013018, @Legoktm wrote:

Can we start sketching out what SUL3 would look like? In my head I currently have an idea that the login link will send you to login.wikimedia.org with ?uselang and original URL preserved, then you log in, including 2FA, it redirects you back to where you came from with an OAuth style handshake. Then on another wiki family, you have to click login, but once you hit login.wikimedia.org it immediately redirects you back and you're now logged in. I'm not sure if there's a way to transparently do the wiki logins without redirecting back and forth...

Similar issue to T234569: Special:Contributions – add 'pinning' functionality to collapsible form?.

@TheDJ told me not too long ago that this was deliberately considered in the design of TemplateStyles. I haven't found the documentation that makes that a true statement, but he said so, so it must be true. :)

In T309574#8011042, @TTO wrote:

In T309574#8008914, @Izno wrote:

This is supposed to have five lines, where the second and fourth lines are blank:

I see this as expected behavior. Do you have proof that these used to be rendered?

Surely expected behaviour would be what the web UI does in this case, namely, to actually render a blank line:

Otherwise it's impossible to tell where the blank lines are. You want to be 100% sure of what you are doing with AWB lest you are accused of being careless, and this doesn't help.

To prove my point further, the task description should have said "first and fourth lines"...

This is supposed to have five lines, where the second and fourth lines are blank:

I see this as expected behavior. Do you have proof that these used to be rendered?

The styling is a result of the fact that AWB's renderer is based on some old version of IE I think, as AWB also fails to render styles from TemplateStyles correctly in Preview.

The last time I deployed the indicator version I reverted because of two issues. One was expected (things still weren't lined up right, probably just a matter of deleting all the CSS) and one was unexpected: I broke the relevant Lua module which depended on the relevant ID existing somewhere in the page (at least, I think that was the gist of the error). See https://en.wikipedia.org/wiki/Module_talk:Coordinates#coordinsert_feature_broken.

Seeing as there hasn't been significant discussion here... I intend to remove the plainrowheaders class from Common.css on en.wp (pending a bot and community consensus), which will necessitate wikitext which is directly the topic of this task as well as

Styles included by a template can currently affect content on the page outside of the content generated by that template, but this ability may be removed in the future and should not be relied upon. (See discussion from phab:T155813#2996589 and in phab:T176272.)

In T287997#7987558, @Guarapiranga wrote:

In T287997#7260810, @Izno wrote:

The class seems largely to duplicate wikitable

Is it? I don't recall it working without wikitable.

Thanks Lego. Looks good!

This is ancient behavior. T8200: Linebreaks are mishandled in <blockquote> and <li> and linked tasks look pertinent.

Should we enable Vector 2022's responsive mode? The only downside of doing this is that some users may dislike it, and need to visit preferences to opt-out.

I think the end objective should be (if it isn't already) one skin displayed on both mobile and desktop domains. Making it 'responsive' in this way moves us in that direction. Yes, a million times yes.

Matma left a comment onwiki to which I've responded there, but I'll copy-paste here so as to centralize discussion.

Not that I am aware of. That's the cost of using a more or less custom formatting.

You need to configure your TemplateData using the format parameter for the template of interest.

Is this task actually resolved? There is nothing in the interface to indicate this can be done.

The rendering relies on tables. Nested tables. Each block is a table mw-hiero-outer and each group of glyphs is another table mw-hiero-table.

Relevant to T43869: ".mw-hiero-table td { vertical-align: middle; }" is overridden when embedded in other tables. and T184221: Conflict between WikiHiero Egyptian hieroglyphs and Minerva and T210695: Hieroglyphs are no longer inline.

• The use of vevent in this way is unintentional. It might be good to remove it (as a very, very low-priority task)
• The use if vevent in this way is intentional and capture the intention in this task.
• The use of vevent in this way is intentional but it is not complete, and refer to the task that would make it complete.

This should be fixed after https://gerrit.wikimedia.org/r/c/css-sanitizer/+/562681 is in a new release of css sanitizer.

filter is explicitly disallowed in Sanitizer::checkCSS. I think this request should be rejected.

In T300695#7926120, @matmarex wrote:

It looks like we accidentally fixed the original issue by way of T305971: Change styling for Minerva/MobileFrontend section headings to use flexbox instead of table-cells, so this task may no longer be necessary.

In T307848#7911820, @Aklapper wrote:

This sounds like T68747#702268 (and to some extent T143535 and T282984#7098855) to me.

In T307753#7911690, @Mathglot wrote:

Not sure how to properly link related tickets, but Izno mentioned T53736 ("Consider changing wikipage redirects to be proper HTTP redirects"), in the context of the discussion at WP:VPT (at @21:05, 7 May).

Does anyone use watchlists on Wikidata? The expiry time doesn't have to be the same everywhere.

I did when I edited there. Mostly to catch vandalism to widely used items, BLP items, and to monitor community discussions. (Though I was also one of the pathological sorts who used the 'add pages you edit to watchlist', I couldn't tell you the reason why I had that option on.)

Based on the comment about audio files, I've closed as a duplicate of the task tracking that activity.

In T222678#7882741, @Reedy wrote:

In T222678#7881652, @Izno wrote:

@Reedy https://gerrit.wikimedia.org/r/c/css-sanitizer/+/562681 supporting Images 3 of the particular version linked in that patch suggests this one should be supported now, but I am getting filtered after submission of an edit form. Was this missed?

The patch only exists in master. No release of css-sanitizer has been tagged since that commit landed, so hence it hasn't been integrated into TemplateStyles yet - https://github.com/wikimedia/css-sanitizer/compare/v3.0.2...master

In T268955#6657780, @Izno wrote:

In T268955#6657404, @Tgr wrote:

(There is a patch that I think does a lot of this but needs to be reviewed.)

That patch could use a task, yeah.

In T306660#7881292, @Jdlrobson wrote:

Also, I think this behaviour interferes with responsive design based on screen width: if I want my templates to react to the available space, I now have to calculate the width of the content instead of the full screen for Vector 2022 (so no more 720px breakpoints).

This is the big flaw with media queries and why many people have been pushing for container queries:
https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Container_Queries

This is not a new problem, we already had this issue as people write responsive rules with legacy Vector in mind which work differently on Minerva. Unfortunately, the only way to support all skins is to have different breakpoints for different skins (I remember hitting this problem when working on the English Wikipedia main page)

invert() can also be spelled invert(100%), which is supported.

As a minor note, perspective isn't mentioned at all in the version of Transforms 1 that https://gerrit.wikimedia.org/r/c/css-sanitizer/+/562681 implemented.

@Reedy https://gerrit.wikimedia.org/r/c/css-sanitizer/+/562681 supporting Images 3 of the particular version linked in that patch suggests this one should be supported now, but I am getting filtered after submission of an edit form. Was this missed?

@Reedy https://gerrit.wikimedia.org/r/c/css-sanitizer/+/562681 supporting Text 3 of the particular version linked in that patch suggests this one should be supported now, but I am getting filtered after submission of an edit form. Was this missed?

So, your example is spelled wrong, Images 3 is to bottom. It's also definitely supported as of https://gerrit.wikimedia.org/r/c/css-sanitizer/+/562681 .

• longer-term it would be good to re-evaluate the value of the toolbar on those pages

Twinkle as a widely-used gadget of interest would need to have a home. I am sure there are other gadgets that need a home on special pages.