You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2023. It is now read-only.
For testing widgets independent of their install-location, we'd like to help the user to specify the location of the require_config.js without modifying the spec_runner.html.
This could be implemented through a URL parameter, but we need to make sure that this parameter cannot be abused to execute arbitrary scripts under the origin of the spec-runner's site.
For example, we could allow only a number of levels to go up (-1 might go straight to the root).
The text was updated successfully, but these errors were encountered:
To stay safe, we can allow to specify a numeric depth level.
The level is used to look up the require_config.js relative to the location of the spec_runner.html. The default would be 4 (../../../../require_config.js).
The example HTML spec-runner (for browser-use only) now allows to specify where to look for the require_config.js.
By default, the configuration will be searched as if the spec-runner was used by a widget installed under includes/widgets/{category}/{widget-name}. To use a different location, pass the URL parameter folderDepth={x} to the spec-runner, where x is the number of URL segment to go upwards for finding the require_config.js.
For testing widgets independent of their install-location, we'd like to help the user to specify the location of the require_config.js without modifying the
spec_runner.html
.This could be implemented through a URL parameter, but we need to make sure that this parameter cannot be abused to execute arbitrary scripts under the origin of the spec-runner's site.
For example, we could allow only a number of levels to go up (-1 might go straight to the root).
The text was updated successfully, but these errors were encountered: