Note: "Topic Containers" and "Clear Affordances" should still appear for people who enabled the Vector Legacy setting within Special:Preferences#mw-prefsection-rendering` whereas the "Page Frame" interventions (ToC) + Sticky Header will NOT appear in Vector Legacy.

What about other skins: Minerva, Monobook, Timeless as well as the unsupported and no longer selectable, but still existing Modern and Cologne Blue? Those parts that apply to legacy Vector could probably apply to other skins as well. Also, I don’t think testing Vector but not Minerva on mobile makes much sense, using Vector on mobile is quite an edge case.

In T305655#7848575, @Tacsipacsi wrote:

Note: "Topic Containers" and "Clear Affordances" should still appear for people who enabled the Vector Legacy setting within Special:Preferences#mw-prefsection-rendering` whereas the "Page Frame" interventions (ToC) + Sticky Header will NOT appear in Vector Legacy.

What about other skins: Minerva...

Ah, good spot, @Tacsipacsi. I specified "Mobile" as a platform the prototype should support without specifying that it also support "Minerva"...task description updated.

...Monobook, Timeless as well as the unsupported and no longer selectable, but still existing Modern and Cologne Blue?

You can expect a comment from me in the next week or so addressing what skins – beyond New Vector, Vector Legacy, and Minerva – the Usability Improvements will be compatible with.

In the meantime, what skins would you expect the Usability Improvements to be compatible with? And if you can bring language to it, I'd value knowing what contributed to this expectation.

(@ppelberg to finalize whether all [ reply ] links will be styled the same way or styled differently depending on whether the comment to which the [ reply ] link is connected is indented)

Per the conversation @iamjessklein and I had today, to start, all reply buttons will be styled in the same way, regardless of whether the comment to which the button is connected is indented or not.

Note: I've updated the task description to reflect this decision to style all reply buttons in the same way.

In T305655#7849995, @ppelberg wrote:

task description updated.

Please make it clear what exactly is in scope for Minerva. According to the note, the sticky header changes won’t be available on legacy Vector—but you didn’t write they won’t be available on Minerva either, even though neither Minerva has a sticky header.

In the meantime, what skins would you expect the Usability Improvements to be compatible with? And if you can bring language to it, I'd value knowing what contributed to this expectation.

I’d expect them to be available on all skins unless a skin is by design incompatible with them (this currently means that the ToC improvements and the sticky header button may not be available in any skin other than new Vector). Of course I don’t expect active support for deprecated skins (Modern, Cologne Blue), but I see no reason not to make Usability Improvements that only touch the content area available there. Just because I happen to use Timeless (or even Cologne Blue), I might want to use topic containers; the skin and Usability Improvements preferences are orthogonal.

• 2. How – if at all – should section edit links be displayed for H3s and H4s?

This question surfaced during the team meeting we had on 13 April.

@iamjessklein talked about this after and have to think that section edit links should continue to be displayed next to === H3 === and ==== H4 ==== section headings.

Note: @Esanders implemented the above already. See: https://patchdemo.wmflabs.org/wikis/484c06ac07/wiki/Talk:DiscussionTools#H3 .

In T305655#7850296, @Tacsipacsi wrote:

In T305655#7849995, @ppelberg wrote:

task description updated.

Please make it clear what exactly is in scope for Minerva. According to the note, the sticky header changes won’t be available on legacy Vector—but you didn’t write they won’t be available on Minerva either, even though neither Minerva has a sticky header.

Good spot. I've updated the task description in T305655#7874540; please let me know if you see any remaining ambiguities in the scope.

In the meantime, what skins would you expect the Usability Improvements to be compatible with? And if you can bring language to it, I'd value knowing what contributed to this expectation.

I’d expect them to be available on all skins unless a skin is by design incompatible with them (this currently means that the ToC improvements and the sticky header button may not be available in any skin other than new Vector). Of course I don’t expect active support for deprecated skins (Modern, Cologne Blue), but I see no reason not to make Usability Improvements that only touch the content area available there. Just because I happen to use Timeless (or even Cologne Blue), I might want to use topic containers; the skin and Usability Improvements preferences are orthogonal.

This is helpful context. We talked about skin support as a team this week and converged on the below. I've also created T306730 to make this information/decision easy to reference in the future.

As @Esanders, @iamjessklein, and I talked about offline today, Ed is going to investigate the work involved with adding the Add topic button within the sticky header to the desktop version of the prototype.

Note: we made the decision to add the Add topic button to the site-wide sticky header on desktop in T304187#7862352 and the work to implement this for use in production will happen in T304187.