About the Firefox supoort

I noticed that some codes for supporting the Firefox had been checked in google code of webpagetest. It’s a great news.
Can I get when this feature will be completed?
Will wptdrvier.exe support IE in the similar way as it does Firefox?
I know that urlBlast.exe supports IE. But I noticed that the codes of urlBlast.exe are much more than those of wptdriver.exe and the codes of wptdriver.exe are neater and cleaner. :slight_smile:

Yep, we’re actively working on Firefox support and hope to have the basics implemented and working within the next 1-2 months. Eventually the IE support will also be moved into wptdriver and everything will share the same codebase (but that is further out).

I found the codes supporting firefox had been checked in google code of webpagetest by r460 (http://code.google.com/p/webpagetest/source/detail?r=460), so I tested it on my local machine. But it seems that it does not work. The firefox can be started up successfully, but after that, nothing else happens and firefox started up will not be closed for ever. wptdriver.exe just hangs on there.
So what should I do to make this work?

However, after I manually copied the directory “%WPTDIR%\firefox\extension\wptdriver@webpagetest.org” to the directory “C:\Program Files (x86)\Mozilla Firefox\extensions\wptdriver@webpagetest.org”, everything went well.
Although it works finally, I think this manual copy operation can be executed automatically. I think it can be written in python file profile_setup.py. It’s just an advice from me. :slight_smile: Anyway, it works, so I want to thank you for your great job.

Yeah, at this point we JUST got it working on a developer workstation so it’s certainly not ready for prime time.

Sometimes Firefox can NOT be closed normally. After that, wptdriver.exe can not work well. Does it happen on your instance?

The reason is I set the configuration parameter “debug” as 1 in wptdriver.ini. If this configuration parameter is set to 1, the method “WptDriverCore::KillBrowsers()” actually does nothing. After I set this configuration parameter to 0, Firefox can be closed forcefully. However, even this configuration parameter is set to 1, Chrome works well. So I think it’s possible that the support for Firefox still has some issues about it.

I found that chrome also has the same problem.

Yes, again, the Firefox support is not even public yet and the Chrome support is still a work in progress. If you’re going to be building off of the trunk and using it things WILL break. Feel free to submit patches for anything you discover :slight_smile: