Advanced script capture settings
You can configure advanced capture settings that will be passed to the Rigi script when capturing HTML previews. To do so, switch the Advanced capture settings toggle on while adding or editing a URL.

An additional field with an empty JSON object value, {}, will be displayed. This field must contain a valid JSON object.
Important
Only use this setting if you experience runtime errors during capturing.
Some web applications will raise runtime errors during HTML preview capturing. This can be caused by strings that contain HTML elements. You can try to avoid those errors by setting the skipHtmlTexts
variable to true. In this mode, the Rigi script will not replace texts on the page (DOM), and the Rigi tokens will stay on the page.
Assume that the developers defined a string with an HTML tag in their resource file:
key="__Hello <subElem>great</subElem> world__"
This will show in the HTML of the live application like this:
<topElem>__Hello <subElem>great</subElem> world__</topElem>
When Rigi is active on the live site (for example, during capturing, live translation, or live review), Rigi replaces the entire topElem
inner HTML with a new string at runtime. As a result, the subElem
in that inner HTML is a new element: it no longer has a connection with the topElem
.
When the code tries to access the original subElem
, it will result in an error.
To avoid such behavior at runtime, set skipHtmlTexts
to true
in the Advanced capture settings. This will prevent the Rigi script from replacing texts that contain HTML elements.
{ "skipHtmlTexts":true }
Rigi can still replace strings in captured HTML previews.