judovana You could start by opening PRs for any of the hasClassName / addClassName tickets. They are the easiest to fix, since the replacement is trivial, e.g.:
diff --git a/core/src/main/resources/hudson/PluginManager/_table.js b/core/src/main/resources/hudson/PluginManager/_table.js
index 4ce767a279..b9a272c755 100644
--- a/core/src/main/resources/hudson/PluginManager/_table.js
+++ b/core/src/main/resources/hudson/PluginManager/_table.js
@@ -9,13 +9,13 @@ Behaviour.specify("#filter-box", "_table", 0, function (e) {
.concat(document.getElementsBySelector("TR.unavailable"));
var anyVisible = false;
for (var i = 0; i < items.length; i++) {
- if (
- (filterParts.length < 1 || filter.length < 2) &&
- items[i].hasClassName("hidden-by-default")
- ) {
- items[i].addClassName("jenkins-hidden");
- continue;
- }
+ if (
+ (filterParts.length < 1 || filter.length < 2) &&
+ items[i].classList.contains("hidden-by-default")
+ ) {
+ items[i].classList.add("jenkins-hidden");
+ continue;
+ }
var makeVisible = true;
var pluginId = items[i].getAttribute("data-plugin-id");
When filing the PR and filling out the Testing Done section, try exercising that code path in your browser and setting a breakpoint on the changed lines in the JavaScript debugger to ensure the new code works the same way as the old code.
Another way to help would be to work on the Ajax.Request tickets. The code for these is harder to write, but Tim has already written much of it in https://github.com/jenkinsci/jenkins/pull/7781 pending testing. So to fix one of those tickets, find the code in Tim's PR, extract it into a new PR, and test as I described above. If it works, then that PR can be merged and Tim's draft PR can shrink. The idea is that as pieces are tested and merged, Tim's draft PR would shrink down to zero eventually.
judovana You could start by opening PRs for any of the hasClassName / addClassName tickets. They are the easiest to fix, since the replacement is trivial, e.g.:
When filing the PR and filling out the Testing Done section, try exercising that code path in your browser and setting a breakpoint on the changed lines in the JavaScript debugger to ensure the new code works the same way as the old code.
Another way to help would be to work on the Ajax.Request tickets. The code for these is harder to write, but Tim has already written much of it in https://github.com/jenkinsci/jenkins/pull/7781 pending testing. So to fix one of those tickets, find the code in Tim's PR, extract it into a new PR, and test as I described above. If it works, then that PR can be merged and Tim's draft PR can shrink. The idea is that as pieces are tested and merged, Tim's draft PR would shrink down to zero eventually.