These are easy to add. Holding off until usage of "wikipage.content" is slightly more widespread and we have more use cases for these (e.g. will HotCat be able to use this? etc.)

If you need one of these hooks, please let it know here including a brief description of how/where you'd like to use it. That'll help to shape the details of exactly where these hooks would go.

As the Target Milestone on this ticket has been set to 1.22.0:

According to http://lists.wikimedia.org/pipermail/wikitech-l/2013-September/072030.html "MediaWiki 1.22 is slated for release on November 30th, at the very latest."

If this is still intended to get fixed for 1.22.0, a patch is needed soon.

[Bumping TM as MediaWiki 1.22.0 tarball was released today.]

Removing target milestone that was in the past.

If you want this in a specific release, have a good reason AND you are willing to find resources to fix this bug, feel free to change it to something appropriate.

So, now that I'm so much further along with LivePreview, I'm pondering taking on some of these elements next. I was thinking starting with templatesUsed, hiddencats and limit report (I've selected them because they are EditPage only elements, should be a safe start).

Do we still agree that this is the right approach ? Or have ideas changed over the past 2 years ?

Change 218275 had a related patch set uploaded (by TheDJ):
Add a wikipage.diff hook

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

Change 219629 had a related patch set uploaded (by TheDJ):
Add wikipage.categories and wikipage.languages hooks

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

Not mentioned yet, but IMHO makes sense, too: #firstHeading

Change 218275 merged by jenkins-bot:
Add a wikipage.diff hook

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

In T53583#1606076, @Schnark wrote:

Not mentioned yet, but IMHO makes sense, too: #firstHeading

Why?

Is this resolved? If not what's left to do?

In T53583#1844576, @Krinkle wrote:

In T53583#1606076, @Schnark wrote:

Not mentioned yet, but IMHO makes sense, too: #firstHeading

Why?

There are tools that modify the first heading, for example append a link to edit the lead section only. or to change the heading via JS in cases where DISPLAYTITLE can't be used (e.g. fr:J sharp), just to name two examples. These scripts should run again when the content was updated.

Apologies and thanks for clarifying.

Patch open is:
https://gerrit.wikimedia.org/r/#/c/219629/

Rebased that patch to only cover the categories case (as it is analogous to diffs). langlinks first need templates per skin probably.

Triggering wikipage.categories post-save in VisualEditor will help HotCat. However triggering it in edit preview might be unexpected in the particular case of HotCat since it probably shouldn't be creating an edit interface for categories whilst on an edit page for wikitext already (since the two would conflict). Something to consider with regards to separation of concerns.

@Krinkle, probably yes, but I think that is a concern for HotCat, and not for the hook I would assume.

Change 219629 merged by jenkins-bot:
Add wikipage.categories hook

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

In T53583#1885706, @TheDJ wrote:

@Krinkle, probably yes, but I think that is a concern for HotCat, and not for the hook I would assume.

True, but if HotCat shouldn't use it, then that leaves the use-case question empty for this hook. Which means I may want to revert it. (It got merged meanwhile by @Jdlrobson)

@Krinkle you do not think there is enough value if hotcat only hooks into this after VE saved the page ?

In T53583#1918917, @TheDJ wrote:

@Krinkle you do not think there is enough value if hotcat only hooks into this after VE saved the page ?

That is valuable, but isn't compatible with using this hook. It would either need to hardcode VE, make exceptions for preview, or simply use the 'wikipage.content' or 'postEdit' hook instead. There doesn't seem to be an appropiate way for HotCat to use 'wikipage.categories' in that case.

Hm.. might make sense to fire the Language portlet from individual skin scripts, rather than making core responsible. That also avoids shipping potentially dead code to all skins (e.g. Minerva where it wouldn't be used).

Although this certainly has been discussed somewhere already, I'd suggest adding classes .mw-diff and .mw-catlinks, that would be used instead of table.diff and .catlinks respectively (of course, keeping these for BC).

And we could still keep the [data-mw="interface"] attributes, for cases we want to be really sure to avoid matching user-generated markup.

Refs https://github.com/wikimedia/mediawiki/commit/b1e3f9e38d7c74e080e99e58dac55629b9f0b097