Export to GitHub

firephp - issue #186

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


Posted on Jan 25, 2012 by Quick Horse

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.

Comment #1

Posted on Jan 25, 2012 by Happy Camel

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

Thanks for the test case.

Comment #2

Posted on Jan 25, 2012 by Happy Camel

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.

Comment #3

Posted on Jan 25, 2012 by Happy Camel

(No comment was entered for this change.)

Comment #4

Posted on Jan 26, 2012 by Massive Lion

Please see attached error message

Attachments

Comment #5

Posted on Jan 30, 2012 by Happy Camel

I have updated the "Tools" page to point to the correct download:

http://developercompanion.com/

Comment #6

Posted on Jan 30, 2012 by Happy Camel

(No comment was entered for this change.)

Status: WontFix

Labels:
Type-Defect Priority-Medium