@Catrope recommends that we make it so that initiating suggested edits will not cause a page reload. This will help with issues like:
|Open||MMiller_WMF||T227728 [EPIC] Growth: Newcomer tasks 1.0|
|Open||None||T238171 Newcomer tasks: slow loading time for suggested edit module|
|Resolved||Tgr||T238179 Newcomer tasks: get rid of reload after suggested edits initiation|
- Mentioned In
- T238037: Newcomer tasks: on mobile 'Suggested edits' activation will flash 'Start here' module and Homepage
- Mentioned Here
- T241002: Newcomer tasks: StartEditingDialog should stay open on mobile while the first task loads
T236738: Newcomer tasks: server-side rendered version of suggested edits module
T238037: Newcomer tasks: on mobile 'Suggested edits' activation will flash 'Start here' module and Homepage
T238171: Newcomer tasks: slow loading time for suggested edit module
I think the architectural constraints are:
- we don't want to maintain the HTML structure in two different places (both client and server side)
- we don't want to keep that structure in different places for different modules
- we don't want to move it to the client side for all modules (eventually, maybe, but not now)
That leaves a couple options:
- keep doing everything on the server side, but always output the HTML for suggested edits when it is enabled on the feature flag level, even if the user did not go through the activation process (intro overlay) yet (just hide it in that case). The client-side code will only have to know which blocks to hide / unhide when the user performs the activation. Con:
- the page layout changes significantly on desktop after activation and this would force us to render the old and new one with identical HTML and handle all the rearranging (ie the stuff now done by SpecialHomepage::getModuleGroups) with CSS or maintain client-side JS logic to handle it
- if we want to do T236738: Newcomer tasks: server-side rendered version of suggested edits module there might be a performance hit for the homepage even with suggested edits not activated.
- Expose rendered module HTML via an API, after suggested edits activation fetch and display it. Con: same issue with rearranging as above, plus somewhat slower (but T236738 is easy to handle now).
- Use some method of sharing templates between server and client (API, ResourceLoader, put it in HTML...). Probably overcomplication for the module contents, but could be a reasonable way of handling the layout rearranging issue.
I would probably go with a mix of the second and third option - use templates for the pre- and post-activation homepage layout (shared via ResourceLoader, since they are very small), and create a query API endpoint for getting the contents of modules.
The suggested edits module has both server side and client side logic for rendering the module skeleton (the full HTML is mostly rendered server-side via OOUI), so the above is moot. The mixed approach is maybe not ideal in the long term, but for now we can just keep using (or, to some extent, start using) the client-side logic.
Note that the dialog closes sooner than ideal on mobile (when the route is changed), before the first task is loaded. That's not ideal but probably non-trivial to fix (our code is not significantly different for mobile and desktop, so this is probably something introduced by MobileFrontend). Should be fixed at some point but less of a priroity; filed as T241002: Newcomer tasks: StartEditingDialog should stay open on mobile while the first task loads.