Nice. I think if you were actually getting beachballed and can provide
an estimate markup size (or at least an example block to demo),
including that in a bug report would be legitimate - especially if
you've seen the raw-markup approach remedy things. I would be interested
in seeing your patch as
Thanks for the response Chris. Rob Zeigler and myself dug in and
figured out a temporary workaround... by overriding (the internal and
subject to change) AjaxPartialResponseRenderer ... I didn't yet do
the elegance of making the change based on the requested Content-
Type, but that would be
Hi Steven,
Regarding c):
I was just about to respond telling you that you can return AJAXObject
or an injected block (mark up), and it will work fine, and then I
realized that even markup is wrapped in a JSON envelope. I don't think
this can be changed without changing some T5 code - even if you
Like pouring ajax in my wounds?
Trying to upgrade from 5.0.6, and upgrading all my ajax stuff is killing me...
The issues I've run into (I'm shoehorning things a bit, by just
returning a block from an actionevent handler and grabbing the markup
from the jsonresponse with my AJAX response handler.