google-code-export / firephp

Automatically exported from code.google.com/p/firephp
1 stars 0 forks source link

FirePHP fails to interpret Responses if window.open is called during pageload #186

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What versions and operating system are you using?

OS: Windows 7 Ultimate 64
Firefox: 9.0.1
Firebug: 1.9.0
FirePHP Server Library: Zend Server 
FirePHP Extension: 0.7.0rc5
PHP Version     5.3.9-ZS5.6.0
Zend Framework Version  1.11.11 

What is the problem?
Before Firefox 9.0.1 there was no problem calling window.open while also having 
FirePHP responses ready to be interpreted on the same page call. (Page is 
allowed to open Popup!)

Now the Firebug Network console shows FirePHP Responsemessages on pageload 
which are not rendered.

What steps will reproduce the problem?
Please see testcase at: http://firephp.3wm.de

What is the expected output? What do you see instead?
If you don't allow popups you can see the firephp response being rendered 
corretly. If you allow popups the reponse will fail to render.

Please provide any additional information below.
Worked fine before Firefox 9.

Original issue reported on code.google.com by richard....@googlemail.com on 25 Jan 2012 at 5:07

GoogleCodeExporter commented 9 years ago
Ah, now the log events make sense 
(http://code.google.com/p/fbug/issues/detail?id=5179)!

Thanks for the test case.

Original comment by christ...@christophdorn.com on 25 Jan 2012 at 8:38

GoogleCodeExporter commented 9 years ago
Does this work with http://developercompanion.com/ on the client?

If so then you have hit a limitation of the FirePHP extension.

FirePHP 0.7 is a minimal layer on top of Firebug 1.9 and works within the page 
lifecycle of Firebug. Firebug has an instance per window and since you are 
opening a window it is a new firebug instance and thus FirePHP instance. 
Unfortunately it looks like you cannot launch a new window with Firebug open 
(for FirePHP to be activated for the initial page load).

DeveloperCompanion is a more comprehensive implementation that works with the 
page lifecycle, but also request and application lifecycles. To see all request 
logs you should be able to leave firebug off and launch the DeveloperCompanion 
Console by clicking on the devcomp icon, selecting "Tools" in the window that 
opens and then "Launch" under companion console. (This works without a license.)

Let me know how things go.

Original comment by christ...@christophdorn.com on 25 Jan 2012 at 9:05

GoogleCodeExporter commented 9 years ago

Original comment by christ...@christophdorn.com on 25 Jan 2012 at 9:05

GoogleCodeExporter commented 9 years ago
Please see attached error message

Original comment by b...@gmx.net on 26 Jan 2012 at 8:03

Attachments:

GoogleCodeExporter commented 9 years ago
I have updated the "Tools" page to point to the correct download:

http://developercompanion.com/

Original comment by christ...@christophdorn.com on 30 Jan 2012 at 9:25

GoogleCodeExporter commented 9 years ago

Original comment by christ...@christophdorn.com on 30 Jan 2012 at 9:25