Remove AJAX and extendability from list tables

[nacin]

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.

Considerations:

1. Don't enqueue the JavaScript.

2. Don't add the ajax nonce fields or any spinners.

3. The top pagination input doesn't work. Solution is to only have the pagination input on the top.

4. The search box button shouldn't have a name.

5. Sorting needs to kick back to page one.

6. 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.

7. Postponed until 3.2. 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.

8. 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.

9. The comment river needs to be fixed. (Gary has a patch up)

10. Paging needs to work when using keyboard shortcuts (i.e. pressing J at the bottom of page 1, when there is more than one page).

[nacin]

Patch attached handles points 1 through 6. I'm adding one more, which koopersmith said he can handle.

8. 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.

[ocean90]

Replying to nacin:

I don't see anything in theme.dev.js

​http://core.trac.wordpress.org/browser/trunk/wp-admin/js/theme.dev.js#L33

(A sadly decision :()

[nacin]

(In [17321]) Revert [17270], [17273], see #16166, see #16262.

[nacin]

(In [17322]) Remove AJAX from list tables. first pass. see #16262.

[nacin]

[17322] addresses points 1 through 6.

We'll execute point 7 early this week.

Point 8 needs someone to tear out some JS.

[Denis-de-Bernardy]

So, we're back in alpha? :-D

[garyc40]

removed quick edit and reply links on edit_comments.php for now, until ajax actions are implemented again, neutered setCommentsList() and commentReply in edit-comments.js

[garyc40]

Attached a patch that addresses point 8.

Comment Reply requires ajax, but there's no alternate no-js interface, as far as I know. We might need to work on that as well for 3.1 .

Another thing, the comment list in post.php doesn't work because it requires ajax as well.

I'm really sorry you guys have to make this drastic decision :(

[garyc40]

make commentReply work again, since it works in WP 3.0 and should still work properly in 3.1

[garyc40]

Attached another patch that restores Comment Reply and Quick Edit comment so that it should work as in 3.0. Please disregard my comment above about no-js comment reply for now.

[garyc40]

fix another notice in commentReply, restore comment list functionality in post.php

[garyc40]

neutered theme.dev.js ajax filter as well

[garyc40]

restore AJAX approve / unapprove / spam / trash functionality

[garyc40]

Sorry for the constant annoying stream of patches. I was thoroughly combing through each line of code in "edit-comments.js" and disabling AJAX features or restoring them one by one if they're in 3.0 .

All ajax functionalities that are not depending on list_table have been restored.

However, it's currently not refilling the extra list. Trashing a comment will still add another comment from the extra buffer to the list for a while, however there are only 8 extra comments in the buffer when the page loads.

In 3.0, refilling the extra list is done by submitting the form #get-extra-comments. However as we abstracted things into WP_Comments_List_Table, it got deleted and we have been using listTable.fetch_list instead.

What's the favorable way to proceed with restoring the extra list's functionality? Use the 3.0 approach, or just create a custom ajax request without going through listTable.fetch_list ?

[nacin]

(In [17325]) s/get_list_table/_get_list_table/ in admin-ajax. see #16262.

[markjaquith]

(In [17326]) Several list table JS fixes. restores XHR comment status changes. props garyc40. see #16262

[nacin]

Use the 3.0 approach, or just create a custom ajax request without going through listTable.fetch_list ?

What's the difference? I would think restoring 3.0 behavior would be the easiest way. edit-comments.dev.js can probably be largely reverted to the 3.0 state.

[garyc40]

Replying to nacin:

What's the difference? I would think restoring 3.0 behavior would be the easiest way. edit-comments.dev.js can probably be largely reverted to the 3.0 state.

No difference in terms of outcome. It's just that the 3.0 state using a form is a bit messy. I'd go with moving the ajax request out of listTable.

[nacin]

Whatever is least impact and easiest to implement, at this point.

[nacin]

Modifying the 8 original points and adding point 9.

The implicit point 10 is that absolutely everything needs testing to ensure parity with 3.0.

[garyc40]

restore river functionality

[garyc40]

previous patch accidentally includes list-table.js

[markjaquith]

10. Paging needs to work when using keyboard shortcuts (i.e. pressing J at the bottom of page 1, when there is more than one page).

[markjaquith]

Probably best not to work on num 10 if it's going to break the patch for num 9, which is slightly more critical. Patch for num 9 looks sane to me. Can someone else review and weigh in on num 9?

[garyc40]

fix prev / next hotkey when navigating to first / last comment

[garyc40]

The patch I attached fixes point num 10 without affecting num 9. It's not a combo patch though, only fixes num 10.

[garyc40]

don't reload when next or prev buttons are disabled, also don't pass hotkeys_hightlight_(first|last) to pagination links

[garyc40]

Please delete ​garyc40.16262.river.2.2.diff, I attached it by mistake.

​garyc40.16262.hotkey.2.diff is the one you want to look at.

[scribu]

Replying to garyc40:

Please delete ​garyc40.16262.river.2.2.diff, I attached it by mistake.

Done.

[nacin]

Bit confused on which patches do what. Correct me if I'm wrong:

• [17326] handled point 8.

• garyc40.16262.river.2.diff​ handles point 9 (fix the comment river)

• garyc40.16262.hotkey.2.diff​ handles point 10 (make paging work with comment shortcuts)

[garyc40]

Replying to nacin:

• garyc40.16262.river.2.diff​ handles point 9 (fix the comment river)

• garyc40.16262.hotkey.2.diff​ handles point 10 (make paging work with comment shortcuts)

Exactly. Sorry for the confusion.

[markjaquith]

(In [17343]) Fix inter-page navigating on Edit Comments screen when using keyboard shortcuts. props garyc40. see #16262

[markjaquith]

10 is in. Reviewing updated patch for issue 9.

[markjaquith]

Fix small conflict introduced by committing issue 10 fix.

[markjaquith]

(In [17344]) Fix the comments "river." issue 9. props garyc40. see #16262

[markjaquith]

That's all 10. Anything else?

[nacin]

Marking as fixed. New tickets for all new bugs please. Thanks!