Chrome and Firefox for Android can be updated through Play Store.

• Android 5, released in 2014, supports up to Chrome 95 (released in 2021) (3 years old) as well as the latest version of Firefox (2024)
• iOS 14, released in 2020, supports only Safari 14, also released in 2020.

Historically, we've raised the browser support requirements based on a feature we want to use that we think is worth the trade-off. GZWDer is correct that the auto-upgrade features of Chromium- and Firefox-based desktop browsers have meant that we've changed to a rolling three-(ish)-year window, and that doing this for mobile-based devices like iOS Safari and Android Chrome would be a more aggressive change.

• Safari iOS 14: 0.38% of Safari iOS users (0.08% of all)
• Safari iOS 12: 0.5% of Safari iOS users (0.1% of all)
• Safari iOS 11, 13: <0.1% of Safari iOS users (<0.02% of all)

However for Safari, we will drop support for version <14 completely once T367821: Discovery: Deprecation of TLS 1.2 is resolved.

Note:

• Chrome and Firefox use last 3 year version rule. Currently Safari does not use such rule, probably because Safari in iOS can not be upgraded individually.
• The Grade A and Grade C defined are normative only.
  • It does not define which browser will get JavaScript (which is detected via feature check in startup module)
  • Non-JS features must work in all Grade C browsers, and JS features must work in Grade A browsers (but might work in some Grade C ones)
• Using newer JS features is not only blocked by this requirement, but also blocked by T277675: Add native support for ES2016-ES2020 or higher versions. Currently, only features up to ES7 can be used in Wikimedia code, where all Grade A browsers at least supports ES8.

Nope, everything has been taken care of here.

Anything left to do here?

I can't replicate any more and the errors are now trailing off:

Mentioned in SAL (#wikimedia-operations) [2024-11-18T15:11:45Z] <lucaswerkmeister-wmde@deploy2002> Finished scap sync-world: Backport for [[gerrit:1091605|Revert "Allow other input and changes to trigger searchsuggestions to update" (T379983)]] (duration: 08m 14s)

Mentioned in SAL (#wikimedia-operations) [2024-11-18T15:06:38Z] <lucaswerkmeister-wmde@deploy2002> samtar, lucaswerkmeister-wmde: Backport for [[gerrit:1091605|Revert "Allow other input and changes to trigger searchsuggestions to update" (T379983)]] synced to the testservers (https://wikitech.wikimedia.org/wiki/Mwdebug)

Mentioned in SAL (#wikimedia-operations) [2024-11-18T15:03:30Z] <lucaswerkmeister-wmde@deploy2002> Started scap sync-world: Backport for [[gerrit:1091605|Revert "Allow other input and changes to trigger searchsuggestions to update" (T379983)]]

Change #1091605 merged by jenkins-bot:

[mediawiki/core@wmf/1.44.0-wmf.3] Revert "Allow other input and changes to trigger searchsuggestions to update"

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

This is certainly still an issue in vector-2010, able to reproduce and still getting user stories raised in VRT.

Change #1091605 had a related patch set uploaded (by Lucas Werkmeister (WMDE); author: Samtar):

[mediawiki/core@wmf/1.44.0-wmf.3] Revert "Allow other input and changes to trigger searchsuggestions to update"

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

Made it impossible to use keyboard navigation in search. Please don't wait till Monday. Vector 2010 is still the default skin in multiple projects, too.

It is affecting end users, unless this is unrelated:

In T379983#10324771, @TheresNoTime wrote:

searching (Vector 2010) and using arrow keys to navigate the search results is not working as expected (gif below, I am just pressing the down arrow):

Thanks @matmarex and @TheresNoTime for confirming the fix. I think it's okay for this to wait until Monday.

I've made a backport patch — I'm around to do this today if needed, but given it's a Friday can it wait until Monday?

The change caused T379983, reverted.

Looking at the current state of the files: https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/core/+/9cdf8af39240b92258b78300bb8c6ff146626179/resources/src/mediawiki.special.apisandbox I think we can consider this done. The largest files are around 700 lines, which is maybe not great, but not too bad either.

Change #675295 abandoned by Bartosz Dziewoński:

[mediawiki/core@master] apisandbox.js - split TokenParamWidget to separate file

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

Change #674677 abandoned by Bartosz Dziewoński:

[mediawiki/core@master] apisandbox.js - add UtilMixin.setParamInfo

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

Change #649917 abandoned by Bartosz Dziewoński:

[mediawiki/core@master] Split up a bunch more apisandbox classes

Reason:

These patches would need to be re-done from scratch now, as there have been many changes to this code in the meantime. Sorry about that. (Some splitting has also already happened in other patches, e.g. https://gerrit.wikimedia.org/r/c/mediawiki/core/+/1089812 )

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

The patch currently fails tests.

Change #1088731 merged by jenkins-bot:

[mediawiki/core@master] Allow other input and changes to trigger searchsuggestions to update

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

Change #1088731 had a related patch set uploaded (by TheDJ; author: TheDJ):

[mediawiki/core@master] Allow other input and changes to trigger searchsuggestions to update

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