The initial thought I'm having in regard to rendering "ajax" responses back to client browsers is that all of the infrastructure/components in place already do an awful lot of work writing their very important content to IMarkupWriter, so why not use that to sort of bootstrap the abililty to make y
Also,
1) we've added a bug report at dojo for the dropdown issue.
We could try hacking away our own solution, but since it's
really their issue, I'm currently devoting my time to other tacos
bugs.
2-3) In http://tacoscomponents.jot.com/BugReporter/Bug49
i've mentioned a simple solution of having t
I think we can work something out. The easiest/quickest way to have these things resolved (for me at least), would be if you created a new test page under the demo tests folder with some examples of these broken items that I could quickly go in and fix.
I still want to fix them either way of cours
Hi,
We recently tried switching all of our datepickers from the Tapestry
component to the Tacos one since there seem to be compatibility issues
between Tacos and the Tapestry DatePicker. We ran into some issues
though and I was curious if anyone knows of any workarounds:
1. In IE6, if you have a
This has to do with our .script files.
We have to be careful when using
inside the tag. Here's an example:
In AjaxForm.script, inside the unique tag, we have
dojo.require("dojo.io.IframeIO");
which appears correct, BUT if a page has 2 forms,
with only the second one using multipart,
then the d
Here's a preview of the page that displays when
the ajax response is problematic and tacos.debugAjaxResponseError
(that's new)
is set to true:
*The response is either invalid xml or was not generated by
ajaxdirectservice
http://www.mozilla.org/newlayout/xml/parsererror.xml";>XML Parsing
Error: mis
hi,
i'm trying the FisheyeList Component in Tacos4.
http://tacos.sourceforge.net/components/FisheyeList.html
but, generated html page is below.
