Materializes files in a static directory of a user configured server.
Materializes files in a static directory of a user configured server.
Version of withMaterializeInServer
with stronger typing.
Static content directory of the server. The files will be put here. Will get created if it doesn't exist.
URL making contentDir
accessible thorugh the server.
This must have a trailing slash to be interpreted as a directory.
Materializes files in a static directory of a user configured server.
Materializes files in a static directory of a user configured server.
This can be used to bypass cross origin access policies.
Static content directory of the server. The files will be put here. Will get created if it doesn't exist.
URL making contentDir
accessible thorugh the server.
This must have a trailing slash to be interpreted as a directory.
The following will make the browser fetch files using the http:// schema instead of the file:// schema. The example assumes a local webserver is running and serving the ".tmp" directory at http://localhost:8080.
jsSettings( jsEnv := new SeleniumJSEnv( new org.openqa.selenium.firefox.FirefoxOptions(), SeleniumJSEnv.Config() .withMaterializeInServer(".tmp", "http://localhost:8080/") ) )
Materializes purely virtual files into a temp directory.
Materializes purely virtual files into a temp directory.
Materialization is necessary so that virtual files can be referred to by name. If you do not know/care how your files are referred to, this is a good default choice. It is also the default of SeleniumJSEnv.Config.