WordPress.org

Limitations

• HTTP errors(timeout, url error, ...) will not be handled this plugin. When any HTTP error occurs your browser will show a standard error page. This limitation comes from jQuery.js does not handle exceptions while establish async socket.
• This plugin works as long as you use the default posting error page as the WordPress destribution provides. This limitation comes from the plugin's error message discovering logic. Possibly I can add an admin option with which you can specify a XPath used to find an error message block. However it will make the plugin not so simple, so I hesitate to do it.
• Display loations of the loading icon and error message are fixed in the javascript script code.

ChangeLog

• 2007-10-19 0.94
  FIX: Make the plugin to be worked under more Apache web servers, now it does not require Apache's Content Negotiation feature.
• 2007-10-08 0.93
  CHG: Support for WordPress 2.3.
  
• 2007-07-07 0.92
  CHG: $() to jQuery(). Make it working with other plugins, say Gengo, which eliminate jQuery default namespace $().
  
• 2007-06-16 0.91
  BUG: When backing previous page after comment posted successfully users see disabled submit button and loading indicator.
  BUG: Reloaing problem. In IE7, newly posted comment was not updated in the editing window after posting it.
  CHG: Make plugin's javascript to be loaded only when comment form exists.
• 2007-06-15 0.9
  First public version.
• 2007-06-11 0.1
  Initial version.