For the complete documentation index, see llms.txt. This page is also available as Markdown.

web-view

This component displays a web page from a URL, content from a datasource, or custom HTML.

Use jig.document when you need a full-screen web page or message passing from HTML content.

Configuration options

Some properties are common to all components, see Common component properties for the properties and their configuration options.

Core structure

uri

The source to be displayed in the web-view, for example, a URL.

Other options

content

HTML to render in the web-view.

height

The height of the web-view.

isEditable

If set to true, the web-view content becomes editable. This works only with content, not with a uri. Use it in a [jig.fullscreen](/spaces/HcPzbms3kZejTmFd500V/pages/pJexnDt2gmKLRExld1M7).

isTrackingTransparencyRequired

If set to true, Jigx shows the tracking transparency permission modal before opening the URL. The default is true.

allowInAppRedirect

If set to true, Jigx intercepts links tapped inside the web-view and handles them in-app. The default is false.

By default, links keep the existing web-view behavior and load inside the web-view.

Set allowInAppRedirect: true to intercept link taps and handle them outside the embedded page.

  • Jigx deeplinks open inside the app. This includes app.jigx.com/... links and supported custom-scheme links.

  • Cross-solution Jigx deeplinks switch to the target solution, then open the target jig.

  • http and https links open in the in-app browser.

  • mailto:, tel:, and similar schemes open in the system app.

  • If the target solution is not assigned to the user, Jigx shows Solution is not available and keeps the current web-view open.

allowInAppRedirect is off by default. Set it only when you want Jigx to handle links outside the embedded page.

Considerations

  • Use component.web-view in jig.fullscreen when the content should fill the screen.

  • isEditable works with content only. It does not work with uri.

Examples and code snippets

Web-view example (URL)

Web-view with URL
Web-view with URL

In this example, we open a target URL in the web-view component.

If the target URL is tracking data (e.g., cookies etc.), you are required by Apple to ask for user consent using the isTrackingTransparencyRequired option. It will ask for user consent the first time any web view in your solution tries to open a target URL.

Examples: See the full example using static data on GitHub. See the full example using dynamic data in GitHub.

Datasource: See the full datasource for static data on GitHub. See the full datasource for dynamic data in GitHub.

Web-view example (In-app redirects)

Enable allowInAppRedirect when links inside the web-view should open in Jigx, in the in-app browser, or in the system app instead of replacing the current page in the web-view.

Expected behavior:

  • Jigx deeplinks open inside the app.

  • Cross-solution links switch solution first when the user has access.

  • Web links open in the in-app browser.

  • Email and phone links open the system app.

  • Unassigned solution links show Solution is not available.

Web-view example (HTML Content)

Web-view with HTML content
Web-view with HTML content

In this example, we are passing raw HTML content to the web-view component. This can either be inline content (see example below) or content from a datasource. If your HTML content does not render as expected (e.g. font too small etc.) embed the meta HTML tag used in the example below in your HTML content.

Editable web-view content (Fullscreen)

In this example, the web-view component is used to make notes on a job. It is configured in a jig.full-screen to display content from a datasource. The isEditable property is set to true, allowing the text in the web-view to be edited. An execute-entity action ensures the updated HTML is saved to the database.

Editable web-view
Editable web-view

Last updated

Was this helpful?