T306440 has been merged.

https://gerrit.wikimedia.org/r/c/mediawiki/core/+/804591/ has been merged, which means we can set expiry times on local storage items. Along with the above patch I think all the technical barriers to doing this have been lifted.

The above patch partially resolves this issue by setting wgPostEdit when redirecting after save. As VE always redirects after save when creating a new page this should be sufficient for your use case @ifried, however wgPostEdit is still not set after edits to existing pages, so we should leave this task open.

The "created" notification was still working but only because undefined is falsey.

Actually that won't work for page creations because we redirect setting venotify. We can set wgPostEdit when that happens though, based on venotify...

Looks like I made a scope typo in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/VisualEditor/+/791691/2/modules/ve-mw/init/targets/ve.init.mw.ArticleTarget.js

There is code present to set venotify to restored so I assume this is just a regression.

We don't set wgPostEdit (that could probably be adding to jsconfigvars in ApiVisualEditorEdit.php), but when we fire the postEdit hook, the target still exists, so you can check if it's a new page by looking at ve.init.target.pageExists.

It's a regression from Vector classic

There are a few dozens test cases in parserTests.txt where the whole table of contents is asserted, checking things like this encoding issue and also deduplication of duplicate headings. I would suggesting making a Vector-2022 version of these tests.

Per my comment above I propose changing the current wording of the notification from:

• Topic X was removed from page Y

to

• Topic X was archived or removed from page Y

1. Is it possible to filter out/suppress/not notify people about discussions that are moved by bots? If so, how much complexity would implementing this add to this task?

As part of this task, offer people the ability to elect to stop receiving notifications of this sort

You can test the new heading with dtenable=1: https://fa.wikipedia.org/w/index.php?oldid=35343366&dtenable=1#A_report:_IP_Editing_Restriction_Study_on_Farsi_Wikipedia

I like the current amount of whitespace. The proposed spacing looks too tight, and it looks odd that the spacing between comments is equal or greater than the spacing between the comment area and the heading.

In T262066#8141706, @Sunpriat2 wrote:

By typing part of the title in the browser's address bar, you can quickly switch to the tab. In Firefox, you can enter "reply" and the tab is shown - it works. But in Chrome, no results are shown for the "reply"; it will be shown if you enter part of the old title (for example, "patch") - is there any way to update the tab information for it too?

append the banner on the page after loading the parsed content

I do not want to be notified when a discussion gets moved to an /Archive page. This is a normal and routine action. If you are an experienced editor, you will expect it; if you are an inexperienced editor, you may be confused by it (what's archiving?!). It does not deserve my attention. Just make the subscription keep working and don't bother me about it. Notifications are for things that need my attention, not for convincing me that the topic subscriptions software works.

Both are set to 60em, but one is at 16px font size and the preview is at 14px, hence the difference.

1. That should be removed in Vector 2022. I think in classic Vector it is to make the toolbar top border a continuous line.
2. Not really, but I don't think there's a good way to prevent it. Setting overflow:hidden on the toolbar would probably cause many other problems.

The patch above adds "first subscribed" and "latest notification" dates to the table.

Decided with @ppelberg:

• Not to display any display names in the default list when you first press '@'
• If a search string matches a display name, then show any matches, example from task description: Search for "jame" would show "Jdforrester" as a match

Testing extracting display names against our test corpus (which isn't very representative: it include a Village Pump (technical) snapshot, and some other talk pages from fr/ar/pl), I've tried to categorise the results so we can what type of things we would get by pulling in display names. I've excluded any results where the display name is a substring of the username.
Transliteration - these are "good" results and one of the big reasons we should try to support this

"Adil Faouzi -> عادل فوزي"
"Arvedui89 -> Aʀvєδuι"
"Azoee -> Azoée"
"Azoee -> azoée"
"Bander7799 -> بندر"
"Daxipedia -> Daxipedia - 達克斯百科"
"FShbib -> شبيب.."
"Mustafa -> مصطفى"
"Þjarkur -> Thjarkur"
"קיפודנחש -> קיפודנחש (aka kipod)"
// Removing some diacritics?
"شيماء -> شَيْمَاء"

In T262066#8140449, @PamD wrote:

registered myself as a user

The patch above uses the messages:

• Replying on <pagename>
• Starting new topic on <pagename>

https://gerrit.wikimedia.org/r/c/mediawiki/core/+/821353 would probably allow you do this with CSS. Care should be taken to support copying of the title with the original : so it can be used for linking.

See https://github.com/MatmaRex/patchdemo/issues/487

The timezone format on that wiki was changed around 2015 (https://cs.wikipedia.org/wiki/Diskuse:Hlavn%C3%AD_strana/Archiv3). I believe we identified this issue when we were deploying the reply tool, and obviously it affects all tools. Our assumption is that the vast majority of conversations that old have been archived.

I'm still unsure as to why something that's supposed to be part of the interface shows up on parsed HTML

This is also true of section edit links

The use case being you have just edited a page and the banner should be shown. An editor like VE which updates the page dynamically does so by fetching the new page contents from action=parse, so this needs to return the full rendering of the page, including this banner.

Also doesn't show for me. The new topic buttons should not show on any pages with __NONEWSECTIONLINK__ such as this one. Do you have any gadgets enabled that could be causing this? What happens if you load the page in safemode (https://www.mediawiki.org/wiki/Manual:Safemode)?

NB this is just for history pages. Visual diffs have been enabled in VE by default for a long time. I agree this is pretty low risk, the default is still wikitext and this will just show a switcher in the top right.

Yes - just exposing the UI to create them.

The CommentParser will only consider content from the signature back to the next heading to be part of a comment. Sub headings are more often used to break up conversations than be part of a comment.

Screenshot from Slack:

The above three patches fix the three issues in the description respectively.

Since we fixed T301839 this can just be enabled on mobile.

This will ride the train next week, so on each day of the train (Group 0/1/2 Tue/Wed/Thu) we should do some sanity checking on a few wikis in each group, where we look at the main page and some random talk pages.

In T312599#8111840, @Esanders wrote:

In T312599#8110947, @hgzh wrote:

Thanks! Another observation I made: the message also appears on talk page redirects with ?redirect=no (e.g. https://de.wikipedia.org/w/index.php?title=Modul_Diskussion:Radsportplatzierungen&redirect=no). This should also be avoided IMO.

Good spot!

In T312599#8110947, @hgzh wrote:

Thanks! Another observation I made: the message also appears on talk page redirects with ?redirect=no (e.g. https://de.wikipedia.org/w/index.php?title=Modul_Diskussion:Radsportplatzierungen&redirect=no). This should also be avoided IMO.

When the Preview reloads, DISABLE or hide the toolbar:

In T313804#8107793, @Samwalton9 wrote:

This is very cool! I'll definitely see if we can incorporate this into our mobile design if you move ahead with deploying for desktop.

See also T313804

https://patchdemo.wmflabs.org/wikis/e808299dc3/w/index.php?title=Special:UserLogin&returnto=Special%3APreferences&returntoquery=&warning=prefsnologintext2

This patch ^ solves the topic container issue without addressing T298617.

From the patch: