|
Q
|
When I try to use BrowserHawk4J to perform extended property tests from my CFMX page, I just get a blank page in the browser. How can I resolve this?
|
|
A
|
The issue is likley being caused by a tag that is setting EnableCFOutputOnly to YES. Please look through your application logic to locate any EnableCFOutputOnly tag and make sure it is set to NO prior to calling into BrowserHawk. You can then set this value back to YES upon returning from the BrowserHawk call.
Note that the location of the EnableCFOutputOnly tag may not be readily apparent. For instance the EnableCFOutputOnly tag could be set by another application.cfm.
|
