Last modified: 2014-10-08 03:00:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 14123 - (ajax) Make MediaWiki more AJAXy (tracking)
(ajax)
Make MediaWiki more AJAXy (tracking)
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: tracking
Depends on: 5560 12917 15280 18296 24235 31270 35618 54687 2837 4427 6593 7851 9434 11002 12802 13941 14003 14230 14444 17367 19536 22556 40207 55893
Blocks: tracking
  Show dependency treegraph
 
Reported: 2008-05-14 16:21 UTC by Danny B.
Modified: 2014-10-08 03:00 UTC (History)
11 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Danny B. 2008-05-14 16:21:44 UTC
Tracking bug for AJAX issues
Comment 1 Andrew Garrett 2009-07-29 16:38:58 UTC
Adding 'tracking' keyword.
Comment 2 Krinkle 2012-12-16 17:09:03 UTC
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.
Comment 3 Nemo 2012-12-16 17:43:09 UTC
(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.
Comment 4 Krinkle 2012-12-16 18:08:25 UTC
(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.
Comment 5 Mark Holmquist 2013-01-15 00:58:53 UTC
See also bug 41837, related to RESTfulness.
Comment 6 Nemo 2013-01-15 22:43:22 UTC
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.
Comment 7 Nemo 2014-02-11 13:54:13 UTC
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>.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links