Hello,

I opened bug

http://bugzilla.qooxdoo.org/show_bug.cgi?id=4147

I have a working patch, see the bug (this.__frame.src did not work
well, but I came up with something that did). I marked the bug as a
blocker as it always throw an exception on Chrome when using an
iframe!

Jean-Noel

On Fri, Oct 1, 2010 at 4:55 PM, Jean-Noël Rivasseau <[email protected]> wrote:
> Hi
>
> I think this might be a typo yes. But actually, the problem is way
> worse than I thought. This error manifests itself whenever Chrome
> sends an iframe. This does not only happens with cross-domain iframes.
>
> I am investigating currently. At least it helps knowing that nobody at
> Qx knows what this.__form.src means, so I definitely guess it is a
> total error / typo.
>
> On Fri, Oct 1, 2010 at 4:42 PM, Alexander Steitz
> <[email protected]> wrote:
>> Hi Jean-Noël,
>>
>>> This works except on Chrome, where it fails on l. 271 of Iframe.js
>>> because this.__form is undefined. I guess this is because of security
>>> concerns (the code is trying to access something it does not have
>>> access to). But what I dont understand at all is what the code is
>>> supposed to do (so that I can patch it properly). The main thing I am
>>> stuck on is:
>>>
>>>       if (this.__form.src) {
>>>         return;
>>>       }
>>>
>>>
>>> Why is this code there???? I have searched and there is no other
>>> references at all to this.__form.src so what is this code checking?
>> I don't know it exactly, but after a first short look at the code I would 
>> tend to say that this is a typo. I guess what was meant here was
>>
>> --snip--
>> if (this.__frame.src) {
>>  return;
>> }
>> --snip--
>>
>> because this code is the handler function for the "onload" event of the 
>> iframe.
>>
>>> I have noticed that when you add the iframe in Chrome, an onLoad event
>>> is immediately fired so I guess this code prevents the callback from
>>> actually marking the request as already completed... but I really need
>>> more explanations to properly patch this.
>> This might be the problem, yes.
>>
>>> Thanks for any help (if someone can reply quickly... I would be very
>>> grateful as I need to patch this quite urgently in production ;)
>> My advice: patch this code locally and re-test. If the issue is really a 
>> typo create a bug report with a patch attached.
>>
>> cheers,
>>  Alex
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>
>
>
> --
> Jean-Noël Rivasseau
> Directeur
> (1) 778 786 3460 / (33) 01 82 88 05 26
> Kameleoon - morphing the web
> http://www.kameleoon.com/
>



-- 
Jean-Noël Rivasseau
Directeur
(1) 778 786 3460 / (33) 01 82 88 05 26
Kameleoon - morphing the web
http://www.kameleoon.com/

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to