We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 4673
    • 577 Posts
    anybody using the latest of firefox?

    It’s a beta but it sure the hell seems fast!

    phew .... now what kind of bugs should I expect?
      Tangent-Warrior smiley
      • 34162
      • 1 Posts
      In my experience it has some serious issues w/ CSS and JS-- code that works in IE/FF 1.0/Safari won’t work at all in the beta.

      I spent an entire day trying to figure out why some code had mysteriously stopped working, only to eventually realize I was running the beta rather than the release. I switched, and everything went back to working.

      FWIW, I already know the new manager will *not* work in 1.5 Beta.
        • 28042 ☆ A M B ☆
        • 24,524 Posts
        Then I shall stick with my 1.0.4; it seems to be working very nicely. Although I am getting to like Camino more and more.
          Studying MODX in the desert - http://sottwell.com
          Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
          Join the Slack Community - http://modx.org
          • 1764
          • 680 Posts
          I’ve been using it for a while. Definitely some bugs that need worked out though. But it’s all worth it to see the glory of the CSS3 column layout. [insert chorus to Glory Glory Haleleujah here] smiley
            • 18397
            • 3,250 Posts
            MARKSVIRTUALDESK Reply #5, 21 years ago
            @infoclipper

            Which manager version won’t work? T3.2?
              • 1764
              • 680 Posts
              Quote from: Mark at Sep 20, 2005, 05:13 PM

              @infoclipper

              Which manager version won’t work? T3.2?

              I’m pretty sure he’s talking about the completely redone TP4 manager. Travis is the one doing most of the work on it.
                • 34162
                • 1 Posts
                Sorry, too little sleep. Yes, TP4’s manager doesn’t work in Firefox 1.5 Beta. Unfortunately, the defect seems to be within the browser itself, as I couldn’t code around it regardless of what I tried.