#18514 closed defect (bug) (wontfix)
WPautoP via AJAX
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Editor | Version: | 3.2 |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Investing doing wpautop as an ajax request (see http://core.trac.wordpress.org/ticket/17144#comment:9 ).
At the cost of slower tab switching, several bugs could be resolved (and end much complaining about "TinyMCE mangled my code" and "Disable autop" requests).
Patch and/or Proof-of-Concept plugin incoming.
Change History (9)
comment:1
WraithKenny — 21 months ago
- Status changed from new to accepted
comment:2
WraithKenny — 21 months ago
related #11947
comment:3
WraithKenny — 21 months ago
Simple plugin available to test the concept:
http://github.com/WraithKenny/ajax-autop
Tested #11947 an #17537 which are fixed by calling autop via ajax.
comment:4
WraithKenny — 21 months ago
The delay caused by the ajax is < 200ms for my tests (from firebug)
That's totally dependant on the network connection. The delay will naturally be lower when testing on localhost.
comment:7
WraithKenny — 14 months ago
I had forgotten about this ticket. I deleted the test plugin unfortunately.
Yeah, the test was definitely localhost; I didn't consider that it'd be considerably longer live (which it really would be significantly longer).
Nevertheless, Tab switching is generally considered to be a rare event and one that users shouldn't do very often at all, so the length of delay could be acceptable at much longer times I think.
I still think these many months later that this is a good idea... If there's any interest I'll rebuilt the testing plugin...
comment:8
WraithKenny — 12 months ago
- Resolution set to wontfix
- Status changed from accepted to closed
Not worth working on.

related #17537 which was closed as "maybelater"