no... the problem is that innerHTML is readonly for table, tbody,
thead, tfoot, tr, select in IE.
On Sep 15, 2008, at 11:47 PM, Bob wrote:
Just to make sure I understand, are you saying that simply replacing
the 'text/xml' with 'text/xhtml' can cause some issues in IE when the
response includes tables?
On Sep 14, 6:03 am, Tom Occhino <[EMAIL PROTECTED]> wrote:
well, 1.3 will have a few minor api changes to Request, and a few
other nice structural changes that wont affect users, as well as
enhancements and fixes for a bunch of the -more components. We
aren't
going to rush it though, so it probably wont be out for several
months.
how about this though...
Why don't i patch Request.HTML for 1.2.1, just pulling out the XML
stuff? The reason I don't want to do it now is because I will have
to
change the function signature to onComplete / onSuccess to stop
taking
the tree and the elements as the first two arguments. (this will
be a
minor breaking change, and we were trying to make 1.2.1 be a drop in
replacement for 1.2)
What do the user's think? Would anyone be opposed to this small
change so we can fix Request.HTML for non XHTML responses in 1.2.1
instead of waiting until 1.3?
- Tom
On Sep 14, 2008, at 7:48 AM, ethaniel wrote:
Thanks for your work, Tom! I really appreciate it!
Any ETA for 1.3?
On 14 сент, 02:33, Tom Occhino <[EMAIL PROTECTED]> wrote:
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-e
...
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.
