(See T330831: Make postEdit hook reliably support user interaction for background.)

Change 949081 had a related patch set uploaded (by Sergio Gimeno; author: Sergio Gimeno):

[mediawiki/extensions/GrowthExperiments@master] [WIP] Post edit: remove postEditMobile hook handlers

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

It seems that we missed that train long ago :/ I did a quick e2e test of the affected code paths (and non-affected, please comment if there are missing cases). See also T343904. cc @Tgr @Etonkovidova:

I'm investigating forward the wrong messaging issue.

• StructuredTaskSaveDialog: I think we just need to drop the OO.ui.isMobile() branch. Probably needs to happen on the same train as the MobileFrontend patch, I don't see an easy way to make it work with both versions.

I tried to check the StructuredTaskSaveDialog OO.ui.isMobile() branch and what I am observing is that getTeardownProcess method is not reached due to the consistent window reload (?). I guess we need to move the instrumentation call somewhere else. What I don't get is how the instrumentation was done before in the reload path. cc @Tgr

• SuggestedEditSession: nothing to do here, I think. The data.newRevId === null branch will be handled by StructuredTaskSaveDialog instead. newRevId will be loaded on demand via API since the postEdit hook doesn't provide it. The nextRequest isn't needed since postEdit runs reliably after the reload (?).

I agree, removing the handler in https://gerrit.wikimedia.org/r/949081

• I don't think MidEditSignup is affected.

Maybe just tackling the TODO @matmarex left