<overlay><overlay> is a container that does not participate in page layout. It occupies no space itself and requires neither width nor height.
When rendered, the content inside <overlay> is completely detached from the Lynx document flow and promoted to a rendering layer outside of Lynx.
By default, the only child of <overlay> uses the screen dimensions as its width and height. It is recommended to treat it as an independent drawing container for the full overlay content.
Use cases
<overlay> to build a dialog that covers the entire page.<overlay>; simply use position: fixed instead.<overlay> can only have one direct child node.<overlay> itself must set position: fixed.<overlay> as the backdrop container:
width: 100%; height: 100%.z-index: 0.margin) instead of changing the backdrop’s own size.
ios-enable-swipe-backWhen overlay is displayed, 'true' allows swiping right to close the current page, 'false' does not allow it
levelIntroduces the concept of layers, which are divided into four levels. The larger the layer, the closer it is to the bottom. By default, it is the first level. The layers are arranged in order from 1 to 4. The displayed layer is specified and is not affected by the order of display. Within each layer, the arrangement is based on the 'last in, first out' logic. The layer cannot be dynamically adjusted when the overlay is displayed, and can only be adjusted when it is hidden. *
modeSpecifies the level at which the overlay content resides on iOS. window: Mounted on the window, the top level of the app; top: Mounted on the topViewController; page: Mounted on UINavigationController; others: customize the name of class in the client.
visibleControl whether the overlay is displayed
Frontend can bind corresponding event callbacks to listen for runtime behaviors of the element, as shown below.
binddismissoverlayCallback when the overlay is hidden.
binderror| Field | Type | Optional | Default | Platforms | Since | Description |
|---|---|---|---|---|---|---|
| errorCode | string | No | – | Android only | Error code: 0 - Display normally; non-0 - Unable to display, you can try to solve it by using the preloading scheme mentioned below for adapting containers. | |
| errorMsg | string | No | – | Android only | Error message |
Callback when touch on the overlay
bindoverlaytouch| Field | Type | Optional | Default | Platforms | Since | Description |
|---|---|---|---|---|---|---|
| state | OverlayTouchState | No | – | Android only iOS only Clay only | Touch state | |
| x | number | No | – | Android only iOS only Clay only | x position relative to the window, in px | |
| y | number | No | – | Android only iOS only Clay only | y position relative to the window, in px |
Callback when touch on the overlay
bindrequestcloseCallback when the back button is clicked.
bindshowoverlayCallback when the overlay is displayed
LCD tables only load in the browser