Moving this back to in progress to track the config changes to enable the new API. The tasks to support the new API are in QA.

For the thumbnail image showing up, this occurs only when the article has a thumbnail and only for tasks in the preloaded task queue mw.config.get( 'homepagemodules' )[ 'suggested-edits' ]['task-queue'] since thumbnailSource is removed by GrowthTasksApi.fetchTasks but not when fetching extra data.

This is caused by missing back button. This regressed from VE's change to use cancel command for ve.ui.MWBackTool, which is extended by MachineSuggestionsBack. GrowthExperiments maintains an allow list of commands that can be used for structured tasks, since cancel was not in the list of allowed commands, the back tool is deemed unavailable.

Filed T311312: Add an image: optimize ServiceImageRecommendationProvider::processApiResponseData since this is a separate change from supporting the new API.

• ServiceImageRecommendationProvider: we iterate over all 52 responses, which seems excessive
• ServiceImageRecommendationProvider: it seems to fail if a single response doesn't pass validation, which seems wrong? It should skip entries which don't pass validation but should return the set of good recommendations – or maybe just the first one?

Hi @Trizek-WMF, I'm planning to get the last set of changes in by the end of this week so that it can be in next week's train. Will let you know if anything changes.

Declining as this is due to iOS's rubberband scrolling

Hi @KStoller-WMF — could you confirm the wikis where this change should be deployed to? I know the description mentions "our four pilot wikis and French" but let's spell this out since the list does change over time so I wanted to be sure.

On mwmaint1002:

Hi @Sgs, the different messages are from different browsers so the fix should address all of them.

Hi @nettrom_WMF, I wanted to confirm with you the additional field we will be sending for this. I was thinking of adding other_reason field to action_data so that the possible responses for rejection_reason field are uniform regardless of whether this free text field is enabled or not. Does that sound good to you?

A couple of related issues:

1. When additional tasks are being fetched, the next button is not disabled.
2. When navigating to the next task while additional tasks are being fetched, "No more suggestions" is shown and doesn't go away even when there are additional tasks.

On mwmaint1002:

This regressed from T308542: Suggested edits: Populate task queue from server-side. Previously the quality gate config is set when the first task is populated. When the logic was changed to be a task queue, the quality gate config was not set.

With fix:

This was fixed recently in 1.39.0-wmf.14; 2022-05-30.