thc202
thc202
Note that you need to rebase the branch to adjust the changelog.
Users might be relying on the "old" stats key for AF tests, that also has the problem of having to cover all refs vs just one if the user does...
These changes are already being done in #9166.
I'm not sure this should use footer counter, this is not an ongoing background process. The Progress tab is more appropriate for these one offs.
How do you know which tools are used or not?
Please refrain from raising more PRs for the time being.
Lets handle the existing PRs first.
Not all scripts were updated (some still left in the changed scripts), was that on purpose?
I'm referring to scripts that are just here (e.g. `Telerik Using Poor Crypto.js` with `Base64` and `Alert`, `Capture and Replace Anti CSRF Token.js` with `ScriptVars`).
Download the `mac-arm64` from https://googlechromelabs.github.io/chrome-for-testing/#stable not ideal but it would work as expected (you need to update the Selenium options to use the binary from that one).