Quantcast
Channel: Silk Performer
Viewing all articles
Browse latest Browse all 4084

Wiki Page: Silk Performer's support for the showModelessDialog() and showModalDialog() JavaScript methods

$
0
0
Since the release of Silk Performer 15.0, windows generated using the JavaScript methods showModalDialog() and showModelessDialog() are now fully supported. In previous versions of Silk Performer,  windows which were generated using these method types were unsupported, as the resulting window was rendered outside of the Silk Performer browser's application control. For example, if the application used the showModelessDialog() method ( http://msdn.microsoft.com/en-us/library/ms536761%28v=vs.85%29.aspx ), within it's internal JavaScript, a new browser window was opened "outside" of the Silk Performer Browser application, which inevitably the Browser application was unable to detect. Refer to the following image: Note the calls which are rendered within the Browser-driven load test 'Record Window'. The recorder has picked up 3 API calls, - BrowserStart(): which launches the Silk Performer Browser Application - BrowserNavigate(): navigates to the URL - BrowserClick(): Clicking on the 'Display Popup in Modeless Mode' - opens the popup window. However further actions, entered within the Popup itself, have not been recorded. For example, selecting and typing into the 'Text Area', a BrowserSetText() and selecting either the 'Apply', 'OK' or 'Cancel' buttons. To workaround the issue it is recommended an upgrade to Silk Performer 15.0 (which now handles the generated window as an additional tab within the browser application - as opposed to an external window) take place. However if an upgrade cannot be achieved,  the application's internal JavaScript calls will need revised. Current and previous versions of Silk Performer support the use of the JavaScript function 'window.open()', see http://www.w3schools.com/jsref/met_win_open.asp . By changing the application to use this function, the popup is not rendered in an external window, but instead as another 'Browser Tab'.  This means that the popup is still under the control of the Browser Application and the actions will now be recorded. If testing an application which utilizes the showModalDialog() JavaScript method using a version pre Silk Performer 15.0,  the actions carried out within the popup maybe recorded, however they will fail on replay, because as with the showModelessDialog() method, a browser window is generated outside of the Silk Performer Browser Applications control. Note: With Silk Performer 9.5, windows generated are suppressed during a recording session:

Viewing all articles
Browse latest Browse all 4084

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>