User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0b5) Gecko/20100101 Firefox/4.0b5 Build Identifier: Mozilla/5.0 (Windows NT 5.1; rv:2.0b5) Gecko/20100101 Firefox/4.0b5 GMX is a free webmail service comparable to Gmail or Yahoo. It works well with all previous releases of Firefox through 4.0 beta 4. But it does not work with beta 5. Reproducible: Always Steps to Reproduce: 1. Start beta 5 in Safe Mode. 2. Go to http://www.gmx.com 3. Enter your GMX email address and password, and log in. Actual Results: The "loading GMX mail" screen appears, and then nothing else happens. Expected Results: The "loading" screen should go away after a minute or two, and the GMX Home screen should appear.

Does this happen in a fresh profile? http://support.mozilla.com/en-US/kb/managing+profiles

Same thing happens for me using Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b6pre) Gecko/20100908 Firefox/4.0b6pre.

I can reproduce this too with Mozilla/5.0 (Windows NT 5.1; rv:2.0b6pre) Gecko/20100908 Firefox/4.0b6pre ID:20100908040849. Error Console Output: Warning: reference to undefined property b.element Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 2628 ---------- Warning: reference to undefined property this.__listeners[a.$$hash || qx.core.ObjectRegistry.toHashCode(a)] Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 337 ---------- Warning: reference to undefined property a[b + (c ? "|capture" : "|bubble")] Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 338 ---------- Warning: reference to undefined property this.__listeners[a.$$hash || qx.core.ObjectRegistry.toHashCode(a)] Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 344 ---------- Warning: reference to undefined property a.params Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 3444 ---------- Warning: reference to undefined property a.transmitNullValues Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 3444 ---------- Warning: reference to undefined property a.type Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 3445 ---------- Warning: reference to undefined property a.contentType Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 3445 ---------- Warning: reference to undefined property a[b + (c ? "|capture" : "|bubble")] Source file: https://www.gmx.com/client/static/script/compiled-gecko-1-3676277485.js Line: 345 Those JS seems to generate a infinite Loop and make Fx consume high CPU Time/sluggish UI.

Same thing on Mozilla/5.0 (Windows NT 5.1; rv:2.0b7pre) Gecko/20100914 Firefox/4.0b7pre

This may be a problem of the dropped XUL support for lables. qooxdoo, the framework behind gmx.com uses XUL labels in some cases. we already have a bug for that in our qooxdoo bugzilla and we will take care of that soon: http://bugzilla.qooxdoo.org/show_bug.cgi?id=4058

(In reply to comment #6) > This may be a problem of the dropped XUL support for lables. qooxdoo, the > framework behind gmx.com uses XUL labels in some cases. Yup, I'm pretty sure that's it, and am setting a blocker on that one (even without a deeper dig down). I guess leaving this open may be useful in the sense of allowing the issue to be further analyzed and/or even fixed within the qooxdoo framework and avoid (many) duplicates in the meantime. I'd say that afterward it should be marked "invalid"...? > we already have a bug > for that in our qooxdoo bugzilla and we will take care of that soon: > http://bugzilla.qooxdoo.org/show_bug.cgi?id=4058 Adding to the "See also" field.

Will the fix for bug 591198 fix this?

So any news when GMX and other sites affected by this will work again ?

(In reply to comment #8) > Will the fix for bug 591198 fix this? No, the issue was being caused by the assumption that XUL would always be present whenever Gecko is the rendering engine (at client-side application framework level). One can take a look at one of the available patches [1], for curiosity. :-) @gmx folks: The qooxdoo related issue [1] was fixed. Hasn't the site yet upgrade to the latest trunk code (or, at least, applied at least one of the available patches [1], hot-fix style)? If/when so, I'd suggest marking this issue fixed invalid, as the underlying cause was in the (qooxdoo) framework, not in Firefox. ;-) [1] http://bugzilla.qooxdoo.org/show_bug.cgi?id=4058

It looks like GMX are aware: http://forum.gmx.com/forum/posts/list/7018.page

FWIW, Login works now, but Navigation is still broken.

(In reply to comment #12) > FWIW, Login works now, Yes it does. > but Navigation is still broken. What exactly is broken for you?

(In reply to comment #13) > (In reply to comment #12) > > but Navigation is still broken. > What exactly is broken for you? * clicking top right Buttons (Organizer,..., Logout) * occasionally clicking the Items in the left Tree does not select them Besides that, Content Loading is broken too: * "Loading" under the left Tree * "Loading Messages" in main Content Area * If you manage to open the Inbox and click on an Item, no Item Content gets loaded * occasionally I get a nice "Slow Script Warning" concerning http://www.gmx.com/client/static/script/compiled-gecko-1-1653692860.js:2224 Using http://hg.mozilla.org/mozilla-central/rev/f4ea6992e1c6 + new Profile on WinXP. Unsure if this all is by the Site or the Gecko ;-)

(In reply to comment #14) > > What exactly is broken for you? > > * clicking top right Buttons (Organizer,..., Logout) > * occasionally clicking the Items in the left Tree does not select them > > Besides that, Content Loading is broken too: > * "Loading" under the left Tree > * "Loading Messages" in main Content Area > * If you manage to open the Inbox and click on an Item, no Item Content gets > loaded > * occasionally I get a nice "Slow Script Warning" concerning > http://www.gmx.com/client/static/script/compiled-gecko-1-1653692860.js:2224 This was a bug with the nightlies and seems to be fixed with http://hg.mozilla.org/mozilla-central/rev/4bfbc7353fda If you still have these problems please report here.

(In reply to comment #15) Yep, my mentioned Issues are gone. Can this be closed as WFM/Fixed then?

(In reply to comment #16) > Can this be closed as WFM/Fixed then? Come on, gmx/qooxdoo fellows and/or Neil (reporter), take a minute to review and close this issue!... ;-) (I'd suggest marking it fixed/invalid, as the underlying issue was in qooxdoo and not actually in Firefox.)

Sorry Helder, but we can't set the bug to resolved. But it should be resolved because qooxdoo has been fixed and this fix is in gmx.com. So there is no reason to keep this bug open at all.

(In reply to comment #18) > Sorry Helder, but we can't set the bug to resolved. I'm assuming that's because you are unable to, not being the bug reporter. As Neil isn't replying to the bug as well for a while (I'm also assuming he's too busy), I'm closing the bug as invalid, as previously suggest. Please reopen if I'm missing something. Thanks! :-)

FIXED, since the TE issue has been addressed.

(In reply to comment #19) > > I'm assuming that's because you are unable to, not being the bug reporter. As > Neil isn't replying to the bug as well for a while (I'm also assuming he's too > busy), I'm closing the bug as invalid, as previously suggest. I have not received any updates on this bug till today. That's why I have not replied. (Yes, I checked my spam folder. Nothing there.)