I inherited this from the developer that I replaced two months ago. For
every other custom created class (datagrids, etc.) the "var win = this"
works fine, but I will give the "self" a shot to see if that makes any
difference. If not, then the vanilla js will (hopefully) be a band-aid
solution until the issue is resolved.
Everything is (AFAIK) same origin/domain; I cannot think of any part of
this web app that reaches to any other domain for anything. We don't even
use a CDN for MooTools; it's a local document.
Thank you,
JD
On Monday, September 23, 2013 4:03:47 PM UTC-5, Dimitar Christoff wrote:
>
> sorry `window.name` would mean nothing - your naming convention is
> misleading. `win = this` points to your instance. should be `self` :) so it
> looks as if mootools or at least `$` is unavailable on the parent frame.
> you can still achieve the same result by using vanilla js - `parent.frames[
> this.name].document.getElementById('someid').style.display = 'none';`
>
> https://www.mozilla.org/security/known-vulnerabilities/firefox.html - a
> number of security fixes in for XSS and masquerading document.uri that may
> have affected you - is the popup in the same origin (domain/port/protocol)?
>
>
> On 23 September 2013 21:33, Jack Drysdale Jr
> <jack.dry...@gmail.com<javascript:>
> > wrote:
>
>> I'll check the 'this' and the 'window.name' and the loop. How do I look
>> through FF changelog?
>>
>> Thanks,
>>
>> JD
>>
>>
>> On Monday, September 23, 2013 3:17:51 PM UTC-5, Dimitar Christoff wrote:
>>>
>>> well. few things to check without code. first make sure `this`
>>> references your window global object, unclear on how you call hide and what
>>> it's bound to. and that window.name is not undefined, unlikely to have
>>> been changed to read only but you never know. then try to loop through
>>> `parent.frames[win.name]` enumerable global properties to ensure
>>> mootools is actually there and available. you are calling it on the other
>>> object directly rather than reusing local one and passing a new context.
>>>
>>> look through changelog for FF as well to see if any significant bugs or
>>> issues have been addressed or what has been reported. also may
>>> be applicable mootools version used.
>>>
>>> On Monday, September 23, 2013, Jack Drysdale Jr wrote:
>>>
>>>> Hello, everyone.
>>>>
>>>> I'm new to MooTools (started working here in July 2013; I'm from a
>>>> jQuery background), and have just started experiencing an issue that
>>>> didn't
>>>> exist before upgrading a testing FF browser to 23.0.1.
>>>>
>>>> This issue is only in FireFox v23.0.1, not IE7/8/9/10, nor in Chrome
>>>> 24, and did not exist in FireFox v21.0.1.
>>>>
>>>> The project has several included .js files that are MooTools classes
>>>> created by a previous programmer. One is for modal popup windows. Up
>>>> until now, it has worked flawlessly.
>>>>
>>>> In FF23.0.1, whenever a user tries to close the modal by either the "X"
>>>> in the corner, or by clicking "SAVE" in the form contained within the
>>>> modal, FireBug reports "parent.frames[win.name].$ is not a function."
>>>>
>>>> The lines around the line in question are:
>>>>
>>>>
>>>>
>>>>> *hide: function(){*
>>>>> * var win = this;*
>>>>> *
>>>>> parent.frames[win.name].$('id_of_container').setStyle('display','none');
>>>>> // This is the line throwing the error.*
>>>>> * win.popup.addClass('hidden');*
>>>>> * }*
>>>>>
>>>>
>>>> Has anyone else experienced anything simliar, after a FF upgrade?
>>>>
>>>> Thank you,
>>>>
>>>> JD
>>>>
>>>> --
>>>>
>>>> ---
>>>> You received this message because you are subscribed to the Google
>>>> Groups "MooTools Users" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to mootools-users+unsubscribe@**googlegroups.com.
>>>> For more options, visit
>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>> .
>>>>
>>>
>>>
>>> --
>>> Dimitar Christoff
>>>
>>> "JavaScript is to JAVA what hamster is to ham"
>>> @D_mitar -
>>> https://github.com/**DimitarChristoff<https://github.com/DimitarChristoff>
>>>
>> --
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "MooTools Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to mootools-user...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>
>
>
> --
> Dimitar Christoff
>
> "JavaScript is to JAVA what hamster is to ham"
> @D_mitar - https://github.com/DimitarChristoff
>
--
---
You received this message because you are subscribed to the Google Groups
"MooTools Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mootools-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
