Closed
Bug 829118
Opened 12 years ago
Closed 12 years ago
MochaUI stopped working under FF 18
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: i2d.testy+bugzilla, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.97 Safari/537.11
Steps to reproduce:
I installed version 18.
Actual results:
Appliaction based on MochaUI stopped working.
Take a look at this demo:
http://pat.cullen.co.za/project/WindowPicker/Demo/
The screen is blank, the error is "currentInstance is null".
The latest GitHub release of MochaUI also failes catastrophically:
https://github.com/mui/mochaui
// Firefox
if (typeof GearsFactory != 'undefined'){
F = new GearsFactory();
, because typeof GearsFactory is actually "undefined" in this release of FF.
Expected results:
In FF 17 there weren't any JS errors.
Comment 1•12 years ago
|
||
You are using MooTools 1.2.0 and that version contains a known bug , see bug 789036.
Please update your MooTools Version - I assume that this is your page
I confirmed this with a regression range search
Last good nightly: 2012-08-04
First bad nightly: 2012-08-05
Pushlog:
http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=20fc34efd733&tochange=9453cf029b72
Reporter | ||
Comment 2•12 years ago
|
||
Updating Mootools to version 1.2.5 doesn't solve the problem.
Updating to 1.3 or 1.4.5 makes the "currentInstance is null" problem go away, but new problem comes up:
// Firefox
if (typeof GearsFactory != 'undefined'){
F = new GearsFactory();
typeof GearsFactory is actually "undefined" in this release of FF.
And it fails.
None of these problems occurs in FF 17.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Comment 3•12 years ago
|
||
>Updating Mootools to version 1.2.5 doesn't solve the problem.
The MooTools used on that page is still 1.2.0, which as already explained can never work.
Comment 4•12 years ago
|
||
BTW, the remaining code that you say isn't working seems to be trying to do persistence via Google Gears, detecting if it's installed in the users browser:
http://www.hanselman.com/blog/GoogleGearsMaybeAllRichInternetApplicationsNeededWasLocalStorageAndAnOfflineMode.aspx
Google stopped support for Gears 2 years ago:
http://gearsblog.blogspot.be/2011/03/stopping-gears.html
Firefox never included Gears by default so the result you're getting is entirely expected.
Reporter | ||
Comment 5•12 years ago
|
||
Thanks, there is a workaround:
You need add "String.prototype.contains = undefined;" before init mootools core. Or add this row as first row in your core file.
https://github.com/mootools/mootools-core/issues/2402
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•