Remove AJAX and extendability from list tables — at Version 8
|Reported by:||nacin||Owned by:||nacin|
|Milestone:||3.1||Priority:||highest omg bbq|
Description (last modified by markjaquith)
We keep discovering new bugs for the AJAX in the list tables. Some current ones include issues with pushState (browser history is broken), bulk actions URI redirects and resets (which is a worse issue for usability than we thought). These strike at the core of the AJAX component. These are not easy to address, and will require some new API in some cases (such as transients for updated notices).
The leads have discussed this and the decision is to remove AJAX from the list tables for 3.1. Without AJAX, the user functionality is unchanged from 3.0. This allows the re-architecture to be spread over multiple releases.
- Don't add the ajax nonce fields or any spinners.
- The top pagination input doesn't work. Solution is to only have the pagination input on the top.
- The search box button shouldn't have a name.
- Sorting needs to kick back to page one.
- Remove the filters in get_list_table() and merge get_list_table() and require_list_table() into a private _get_list_table(). Mark all tables as private.
- The architecture of the list tables needs to be reviewed this week for potential changes. Right now it isn't at the state where we are comfortable with release, especially when considering future requirements for backwards compatibility. By removing the JS for 3.1, we can spend the next week getting the classes exactly how we want them.
- edit-comments.dev.js and theme.dev.js both declare list-table a dependency. I don't see anything in theme.dev.js, but there are some things in edit-comments.dev.js that will need to be neutered.
Patch to follow shortly.