Cheers to JSON :)
On Fri, Jan 22, 2010 at 12:36 PM, woomla wrote:
> > > Why not use *JSON*? its cross platform cross programming language and
> its
> > > simply awesome!
>
> > [1] Because it is not always available: this example is an RSD feed,
> > among hundreds of popular XML-based format
> > Why not use *JSON*? its cross platform cross programming language and its
> > simply awesome!
> [1] Because it is not always available: this example is an RSD feed,
> among hundreds of popular XML-based formats. When you don't control
> the service nor an intermediate gateway, you don't c
> > Why not use *JSON*? its cross platform cross programming language and its
> > simply awesome!
>
> [1] Because it is not always available: this example is an RSD feed,
> among hundreds of popular XML-based formats. When you don't control
> the service nor an intermediate gateway, you don't
> During testing, I've discoverd one thing. IE requires that the xml has
> a name space.
We talked about this a while back in another thread. I think IE is
doing the right thing. After all, (X)HTML does not have an
anything-goes DTD. If you want to inject els into the DOM, validat
> Why not use *JSON*? its cross platform cross programming language and its
> simply awesome!
[1] Because it is not always available: this example is an RSD feed,
among hundreds of popular XML-based formats. When you don't control
the service nor an intermediate gateway, you don't control the
Why not use *JSON*? its cross platform cross programming language and its
simply awesome!
On Thu, Jan 21, 2010 at 2:04 PM, woomla wrote:
> Thanks for pointing me in that direction. I've got it kind of running.
> I need to test to see if textContent exists at one point because IE
> doesn't have t
Thanks for pointing me in that direction. I've got it kind of running.
I need to test to see if textContent exists at one point because IE
doesn't have that property. I can use innerText, but FF doesn't have
that one. I hope for a Moo solution one day.
During testing, I've discoverd one thing. IE
> No, it doesn't. i.e. $(request.response.xml) returns null becaouse
> request.response.xml.toElement does not exist.
You might try wrapping the IE `xml` attribute using Elements.from:
http://mootools.net/shell/2dupv/2/
-- S.
On Jan 20, 10:11 am, Sanford Whiteman
wrote:
> > Unfortunately, I cannot tell my clients not to use IE, so I need an
> > other solution. Any idea's? My best hope is that IE objects would be
> > mootools extended. There might be other objects that are not.
>
> Wrapping in $() should fix up such i
