Adding 'tracking' keyword.

This tracker is used for issues with the AJAX interface on the server-wide or the client-side code that interfaces with that API.

Removed various dependencies that for components that simply use ajax internally but aren't issues with the ajax interface itself, nor can be fixed by changing anything with ajax.

(In reply to comment #2)

This tracker is used for issues with the AJAX interface on the server-wide or
the client-side code that interfaces with that API.

No, it never was AFAICS.
I'm clarifying the summary, let's see if there's something else not relevant.

Removed various dependencies that for components that simply use ajax
internally but aren't issues with the ajax interface itself, nor can be fixed
by changing anything with ajax.

Moved this new tracking bug to 43175.

(In reply to comment #3)

I'm clarifying the summary, let's see if there's something else not relevant.

You blindly re-added all of it, even the ones that really didn't belong on it either way. I've re-removed those.

Removed various dependencies that for components that simply use ajax
internally but aren't issues with the ajax interface itself, nor can be fixed
by changing anything with ajax.

Moved this to new tracking bug 43175.

Sure, that works.

See also bug 41837, related to RESTfulness.

Should bugs be filed for features like [[m:User:Pathoschild/Scripts/Ajax_sysop]] being added to core (AJAX patrol and rollback from within RC as options)?
I'd normally consider them suitable only as gadgets, but they're currently broken https://github.com/Pathoschild/Wikimedia-contrib/issues/8 and this backfires elsewhere, see bug 8697 comment 12.

Based on code by Yair Rand, [[mw:Extension:Popups]] is being developed, by a developer who seems to work for WMF if the email address can be trusted. I asked some questions at https://www.mediawiki.org/wiki/Thread:Extension_talk:Popups/Patrolling_and_maintenance.