ethaniel, I'm sorry about this problem.
For now, Request.HTML requires XHTML in order to get around problems
with select / table elements in IE (setting the innerHTML didn't work
in MooTools 1.2). I've since added a better Element.Properties.html,
which allows you to set the html of select's and tables, so we will
have a real Request.HTML as well as a Request.XML in MooTools 1.3.
- Tom
On Sep 13, 2008, at 11:02 PM, Tom Van Schoor wrote:
Yeah, they intend to change it in the next release.
Cheers,
TVS
ethaniel schreef:
Yes, this helps. But I don't want to keep this thing in mind every
time I update mootools.
Would be MUCH better if this could be added somewhere as an option to
the current Request.HTML parametres (like
update,evalScripts,onSuccess,etc...).
This way I could easily download the YUI compressed mootools and not
have to modify the source code myself.
On 14 сент, 00:27, Tom Van Schoor <[EMAIL PROTECTED]>
wrote:
There is an easy fix....
Search your mootools-core file for "text/xml" you'll find it
twice, but you'll need the second one = inside the Request.HTML
definition.
Change it to "text/xhtml" and your problem is solved.
Hope that helps,
Tom Van Schoor
ethaniel schreef:I have updated to 1.2 and now found that AJAX
support in Mootools is completely different, than in 1.1. I have
this code: new Request.HTML({url:'/register.php?
checkfreename=1&what='+what,method: 'get',update:$
('logincheck'),evalScripts:true}).send(); (note the update part).
Every time I run it, it spits out a render error in Safari, some
unknown errors in Firefox and Attvalue error in Chrome. When I
read about it, it came clear to me, that Mootools somehow modified
this support and now it works different. Here are the links to
bugtrackers:http://mootools.lighthouseapp.com/projects/2706/tickets/75-ajax-and-entitiespossible
solution:http://mootools.lighthouseapp.com/projects/2706/tickets/182Guys
, could you make this solut
ion work in the current version of Mootools? This 1.2 version was
really quite a pain in the ass for me already and now, when I have
updated most of my website, I find out about this problem and
there is no easy fix. I feel betrayed.
