We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
MODX Community Forums Archive

mootools causing firefox to break

    • 14786
    • 57 Posts
    joshua Reply #1, 19 years, 2 months ago
    This is a new MODx install. When using it normally, clicking any links in the manager including saving/moving/editing documents, Firefox will throw an exception on mootools saying its an unresolved script thats taking too long to load. I get three options, Stop Script, Debug Script, or Continue. Choosing stop script will stop the loading and I have to re-do what I tried to do. Choosing debug script using Firebug takes me to the following mootools function

    function (p, a, c, k, e, d) {
    e = function (c) {return (c < a ? "" : e(parseInt(c / a))) + ((c = c % a) > 35 ? String.fromCharCode(c + 29) : c.toString(36));};
    if (!"".replace(/^/, String)) {
        while (c--) {
            d[e(c)] = k[c] || e(c);
        }
        k = [function (e) {return d[e];}];
        e = function () {return "\\w+";};
        c = 1;
    }
    while (c--) {
        if (k[c]) {
            p = p.replace(new RegExp("\\b" + e(c) + "\\b", "g"), k[c]);
        }
    }
    return p;
}
      • 33372
      • 1,611 Posts
      ZAP Reply #2, 19 years, 2 months ago
      I’ve seen that, too. Only on Windows, however. I use Firefox on Linux most of the time and it’s never happened to me there.

      The computer that has thrown this error a few times lately is kind of old and slow, so I thought that perhaps it was just having a hard time executing the script and Firefox is smart enough to realize that it’s suffering.
        "Things are not what they appear to be; nor are they otherwise." - Buddha

        "Well, gee, Buddha - that wasn&#39;t very helpful..." - ZAP

        Useful MODx links: documentation | wiki | forum guidelines | bugs & requests | info you should include with your post | commercial support options
        • 7396
        • 1 Posts
        digitarald Reply #3, 19 years, 2 months ago
        This function is from Dean Edwards packer, its not a MooTools function. Its called when the browser loads the Javascript files, this function uncompresses the code and loads it via eval. Its weird that it breaks Firefox, download MooTools minfied with JSmin to get a version that is not compressed using eval. Its only known that JS code packed with Deans’s packer loads slow in Konquerer, but not that it breaks in Firefox.
          • 36805
          • 354 Posts
          MrDutchy Reply #4, 19 years, 2 months ago
          I can confirm the issue as I have also experienced this bug but on the frontend of my modx powered website instead of directly in the manager. When refreshing the page when logged into the manager backend the error occurs sometimes but not allways. I guess it really is a mootools issue and because quickedit utilizes it I am experiencing the issues in the frontend. I did not experience this until I started using MODx 0.9.6. on some of our websites (most of them are still running on 0.9.5).

          If digitarald is right this is probably a new bug and maybe the developers should be notified. Until then maybe I will use the IE whenever i need access to the manager or replace my mootools files with the minified version as digitarald suggested.

          I think that, considering the FireFox+Windows compatibility issue, it might be a good idea for the next minor release of MODx to include a mootools version that does not include this packer.
            • 14786
            • 57 Posts
            joshua Reply #5, 19 years, 2 months ago
            So this is definitely an issue in Firefox. I’m at a loss as to the technical details but the manager definitely loads and behaves a lot slower in Firefox. Pretty much all processes take half the time to complete in IE.

            If its happening on the actual website frontend like MrDutchy said thats terrible. Especially since Firefox already looses 75% of the people that download it! I wouldn’t want to give them another reason to switch to IE.
              • 36805
              • 354 Posts
              MrDutchy Reply #6, 19 years, 2 months ago
              Quote from: joshua at Aug 20, 2007, 03:24 PM

              [...]
              Especially since Firefox already looses 75% of the people that download it! I wouldn’t want to give them another reason to switch to IE.
              I read about that and I think it’s a little funny. After all i re-downloaded FF at least 30 times and still use only 2 of them. So much for statistics.
                • 28033
                • 925 Posts
                Soshite Reply #7, 19 years, 2 months ago
                Is there specific components that MODx’s Mootools uses? I had this issue before, so I want to replace the one used in MODx with the JSmin version.
                  My Snippets
                  -> PopUpChunk v1.0
                  • 36805
                  • 354 Posts
                  MrDutchy Reply #8, 19 years, 2 months ago
                  Quote from: Soshite at Aug 21, 2007, 06:38 AM

                  Is there specific components that MODx’s Mootools uses? I had this issue before, so I want to replace the one used in MODx with the JSmin version.
                  Could anyone respond to this? I would like to download a new build of the mootools without Dean Edwards packer. I would need to know which components i need to tick on the mootools download page (http://mootools.net/download) because I do not want a build which includes everything if I don’t have to.
                    • 22303 MODX Staff
                    • 10,725 Posts
                    opengeek Reply #9, 19 years, 2 months ago
                    I’ve only ever noticed this "the script has stopped responding" error when I have a lot of browser windows open and am visiting a bunch of web sites that use too much javascript all at the same time. Or god forbid, if I have a Java applet running in a browser; Fx likes to choke on those. Or if I just have too many applications open and Windows is drowning in it’s own excrement, but perhaps I’m being too graphic. But otherwise, the latest manager in 0.9.6 is the leanest and meanest of the MODx manager interfaces yet, and performs so much faster than it used to.

                    As for your front-end site, get whatever version of mootools you want to use and use it. You’ll just have to consider add-on’s individually, seeing if they have any dependencies on mootools, or specific mootools functions. It shouldn’t be hard to make sure that your mootools distribution will work with your site and the add-ons you’ve chosen to use.

                    There is not and will not be an official js library chosen by MODx. It’s just another element in the web toolbox and you are completely free to build sites or add-ons with or without mootools, or any other js framework or library.
                      Jason Coward
                      Chief Architect @ MODX
                      http://www.jasoncoward.com | http://twitter.com/drumshaman | https://github.com/opengeek
                      • 36805
                      • 354 Posts
                      MrDutchy Reply #10, 19 years, 1 month ago
                      Quote from: OpenGeek at Aug 23, 2007, 11:44 AM

                      It shouldn’t be hard to make sure that your mootools distribution will work with your site and the add-ons you’ve chosen to use.

                      There is not and will not be an official js library chosen by MODx. It’s just another element in the web toolbox and you are completely free to build sites or add-ons with or without mootools, or any other js framework or library.
                      Sure, I understand this. What would be interesting to know is the minimum "mootools build" required by "built-in" MODx parts like Quickedit and some manager javascrpt features. Or are you saying they aren’t using any mootools anymore?