If you experience problems running the Autoprefixer preprocessor on windows, please follow these steps: For some reason, there is a problem with the postcss v8.1.1 release. You will need to downgrade to v8.1.0 manually by opening a command line (cmd or Powershell) and running this command: npm i postcss@8.1.0 After that, run Ghostlab’s preprocessor pipeline […]
If Ghostlab serves your content via HTTPS (i.e., HTTPS is activated in Preferences > Advanced > Security > HTTPS Server), all communications with Ghostlab use HTTPS. If you are using a self-signed certificate, you will need to add certificate exceptions manually for the Ghostlab server IP with the Websocket port in Firefox and Internet Explorer […]
For testing, your web application might be protected using (HTTP Basic) authentication, prompting you to enter a username and password to access the site. Ghostlab can help you in this case (only if HTTP Basic Authentication is used, though): you can add the username and password in Ghostlab so it sends the credentials to the […]
Especially in more complex web applications you might come across situations in which the site fails to function correctly when loaded through Ghostlab, e.g., you get redirected to a wrong URL, a login doesn’t work, fonts don’t load as expected, the page “escapes” Ghostlab’s control and the interactions are no longer synchronized because of this. […]
Most likely, the page has “escaped” Ghostlab’s control. You can verify this by checking the URL in the browser bar. If it’s the regular URL instead of Ghostlab’s server URL (something like http://123.45.67.89:8005/…), the “escape” happened. To prevent this from happening, usually it is enough to increase Ghostlab’s JavaScript rewriting level in the site settings: […]
The sources tab of the inspector will only show JavaScript files if JavaScript debugging is turned on, so please make sure that you ticked the “Debug JavaScript” checkbox. For performance reasons, some JavaScript files aren’t debuggable and won’t appear in the sources list or won’t allow you to set breakpoints. This is controlled by Ghostlab’s […]
If Ghostlab’s inspector doesn’t show the CSS styles, please try reloading the page in the browser. Mostly, they’ll appear. If you’re still using Ghostlab 2, please consider upgrading to Ghostlab 3. The inspector has been improved a lot and is more in line with the current Chrome devtools, and it might just solve the CSS […]
If you experience that mobile devices don’t show up in Ghostlab’s client list and actions aren’t synchronized (but your desktop browsers are there and get synchronized), the reason is most likely a network problem. If all the connected browsers disappear from the client list and the page isn’t synchronized anymore, please have a look a […]
If all your other browsers and mobile devices appear in the Ghostlab’s client list and are synchronized, and it’s just Internet Explorer that doesn’t, please make sure that you are using a version of Internet Explorer that is supported by Ghostlab (IE 9+); Internet Explorer isn’t set to compatibility mode. This will simulate a very […]
Ghostlab tries to cover as much as possible in terms of interaction synchronization, but might fail if you built your own component that uses tricks or fancy events. We’d love to hear about your component! Please get in touch with technical support and send us a minimal example and a description how to reproduce the […]