For cases where Remex changes the rendering, the "edit" link uses the ParserMigration tool that will show a diff of the current rendering, and the future broken rendering... - @ssastry should tidy-font-bug be using parser migration?

In T183746#3862807, @Legoktm wrote:

For cases where Remex changes the rendering, the "edit" link uses the ParserMigration tool that will show a diff of the current rendering, and the future broken rendering... - @ssastry should tidy-font-bug be using parser migration?

Yes, and looks like the edit links anywhere actually aren't showing the parser migration links ... something is broken.

In T183746#3862810, @ssastry wrote:

In T183746#3862807, @Legoktm wrote:

For cases where Remex changes the rendering, the "edit" link uses the ParserMigration tool that will show a diff of the current rendering, and the future broken rendering... - @ssastry should tidy-font-bug be using parser migration?

Yes, and looks like the edit links anywhere actually aren't showing the parser migration links ... something is broken.

I am not sure if they ever did -- I noticed this earlier this month and meant to investigate it, but got distracted. I am heading off on a trip shortly, so will have to wait till Jan unless @Legoktm, you can take a look.

There were never parser-migration edit links in this context, only the linterid edit links.

Change 430026 had a related patch set uploaded (by Subramanya Sastry; owner: Subramanya Sastry):
[mediawiki/extensions/Linter@master] Fix broken test for enabling parsermigration-edit links

https://gerrit.wikimedia.org/r/430026

Change 430026 merged by jenkins-bot:
[mediawiki/extensions/Linter@master] Fix broken test for enabling parsermigration-edit links

https://gerrit.wikimedia.org/r/430026