This task can be summarized as:

• Reimplement the current talk button functionality but...
• Present it as a toggle

With the exceptions noted in AC

We're doing logged in only. No changes to beta mode. Kind of 3 and 4. Needs more detail in task description.

(@Niedzielski , by "makes a change on the client", did you refer to making an edit to a wiki page, or were you talking about a hypothetical new schema logging preference changes on the client side?)

I suppose either. For example, can we track a workflow that starts on the server and concludes on the client?

This appears to still be an issue for large screens:

There is no difference between js and non-js users as Special:MobileOptions page works for non-js users.

Does this mean there is no JavaScript executed on Special:MobileOptions? If there is JavaScript, it would seem to me that we have different options available to us on the server and client.

The context genie has smiled upon me!

That said, there seems little reason for the language and download icons

Now I'm wondering if the language button is useful in the case that it's deleted on one wiki but another :|

There is a fix for this (and tests) in https://gerrit.wikimedia.org/r/#/c/mediawiki/extensions/MobileFrontend/+/460986/ but it comes with too many other changes. It's possible that useful changes may be teased out.

Thank you for your work, @Shreyasminocha! Your patches have been merged \o/

Whatever solution is used, I hope it can use a text label accompaniment as no other solution can be as clear and explicit. Pictures may say a thousand words but icons captioned well with text say one and leave no ambiguity.

can you clarify in the reproduction steps in the task's description when you mean the browser's back/forward button, versus the back/forward controls on the media overlay?

@alexhollender, the dedicated back and forward buttons in the browser chrome available on all webpages. Also, the back button on Android and equivalent back / forward gestures on some tablets.

Do we want to move extendSearchParams.js under src/mobile.startup.js/search as part of this task?

We added @pmiazga as an admin under https://horizon.wikimedia.org/project/member/.

I think T211190 should be a child of this since it's the initial checkin. I've made the change. Please revert if I'm mistaken.

environment with only Popups and EventLogging extensions. Popups were configured to use restbaseHTML gateway

Nice detail!

It wasn't clear what the status of this task was as all subtasks appear to be closed.

Er, and I think this pagelist less?

I think this should be moved too:

Should the following be removed from extension.json?

Looks good to me!

\o/ thank you, @Jdforrester-WMF! I see these changes live now and working properly.

@Jdlrobson, we discussed this briefly in today's standup and believe it's ready to be closed. We're still having ongoing discussions about how to best test views in our patchsets but think the purpose of this ticket to kickstart some of these conversations has been accomplished.