[ https://issues.jboss.org/browse/JBIDE-13967?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13967: ------------------------------------------ [~maxandersen]: bq. Are we doing some custom rewrite rules or how ? In short, yes. Our modification of Ripple works in the following way (original Ripple does the same, but with iframes instead of pop-ups): Let's say, we want to use Ripple for http://localhost:4400/accelerometer.html, then: - we point our SWT browser to http://localhost:4400/accelerometer.html?enableripple=true - the Jetty server responds with {{/ripple/assets/index.html}} in the response body (it is the main page of Ripple, which contains accelerometer, geolocation, etc.) - this page contains a script, which removes {{'?enableripple=true'}} from its own URL parameters and opens http://localhost:4400/accelerometer.html in a pop-up - our code intercept this pop-up opening and set BrowserSim to be this pop-up window Given above, Ripple requires the following rewrite rule to be specified: _If a request contains parameter {{enableripple=true}}, then {{/ripple/assets/index.html}} must be returned in the response._ Also see [ServerCreator.java:87|https://github.com/yradtsevich/jbosstools-vpe/blob/...]. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira