We will look into this. I didnt dig into the new JSON object yet, but
i'm trying to make the mootools implementation compatible with the new
introduced native and probably making use of the (said to be faster)
native implementation. We normally dont support betas or even earlier
versions, but i'm sure the JSON native object will make it into the
next release.
Thanks for the report and digging into this.
Jan, mootools core developer
On Oct 11, 2008, at 18:42, eduacostam wrote:
digging around I've found this:
http://blog.mozilla.com/meeting-notes/archives/66
ths important stuff is:
JS 1.9.1
- New global JSON object, will follow up to match ES 3.1 spec.
more info: https://wiki.mozilla.org/QA/Firefox3.1/Native_JSON_Testplan
Now i've tested mootools without JSON and it works well, so I think
the problem is that firefox added a JSON object and when mootools
declares it's own it brakes everything.
This is a serious problem if Firefox 3.1 is going to have this.
Devs what do you think?
On Oct 11, 12:08 am, "Iván N Paz" <[EMAIL PROTECTED]> wrote:
Im afraid:
redeclaration of const JSON
Might be the issue here... if thats the problem... has JSON become a
reserved word in nightly firefox???
Personally I wouldnt bother too much with that, since nightly builds
are just like that... prone to errors here and there...
Maybe on tomorrow's nightbuild it will be gone... :-P
--
my blog: http://blog.kassens.net
