CustomTabsCallback

const val ACTIVITY_LAYOUT_STATE_BOTTOM_SHEET = 1: Int

The activity is being displayed as a bottom-sheet at its initial height.

const val ACTIVITY_LAYOUT_STATE_BOTTOM_SHEET_MAXIMIZED = 2: Int

The activity is being displayed as a bottom-sheet at its maximized height.

const val ACTIVITY_LAYOUT_STATE_FULL_SCREEN = 5: Int

The activity is being displayed over the whole window. This will be the case when a Partial Custom Tab bottom sheet or side sheet cannot be displayed due to minimum width restrictions (see EXTRA_INITIAL_ACTIVITY_WIDTH_PX) or browser limitations.

const val ACTIVITY_LAYOUT_STATE_SIDE_SHEET = 3: Int

The activity is being displayed as a side-sheet at its initial width.

const val ACTIVITY_LAYOUT_STATE_SIDE_SHEET_MAXIMIZED = 4: Int

The activity is being displayed as a side-sheet at its maximized width.

const val ACTIVITY_LAYOUT_STATE_UNKNOWN = 0: Int

The activity's layout state is unknown. This value communicates an error state, the fact that the state cannot be determined, or that the browser implementation does not provide support for this feature.

const val NAVIGATION_ABORTED = 4: Int

Sent when loading was aborted by a user action before it finishes like clicking on a link or refreshing the page.

const val NAVIGATION_FAILED = 3: Int

Sent when the tab couldn't finish loading due to a failure.

const val NAVIGATION_FINISHED = 2: Int

Sent when the tab has finished loading a page.

const val NAVIGATION_STARTED = 1: Int

Sent when the tab has started loading a page.

const val TAB_HIDDEN = 6: Int

Sent when the tab becomes hidden.

const val TAB_SHOWN = 5: Int

Sent when the tab becomes visible.

fun extraCallback(callbackName: String, args: Bundle?): Unit

Unsupported callbacks that may be provided by the implementation.

Note:Clients should never rely on this callback to be called and/or to have a defined behavior, as it is entirely implementation-defined and not supported.

This can be used by implementations to add extra callbacks, for testing or experimental purposes.

fun extraCallbackWithResult(callbackName: String, args: Bundle?): Bundle?

The same as extraCallback, except that this method allows the custom tabs provider to return a result. A return value of null will be used to signify that the client does not know how to handle the callback. As optional best practices, KEY_SUCCESS could be use to identify that callback was *successfully* handled. For example, when returning a message with result:

    Bundle result = new Bundle();
    result.putString("message", message);
    if (success)
        result.putBoolean(CustomTabsService#KEY_SUCCESS, true);
    return result;

    Bundle result = extraCallbackWithResult(callbackName, args);
    if (result.getBoolean(CustomTabsService#KEY_SUCCESS)) {
        // callback was successfully handled
    }

fun onActivityLayout(
    left: @Dimension(unit = 1) Int,
    top: @Dimension(unit = 1) Int,
    right: @Dimension(unit = 1) Int,
    bottom: @Dimension(unit = 1) Int,
    state: Int,
    extras: Bundle
): Unit

Called when the Partial Custom Tab's layout has changed. This callback is not applicable to Custom Tabs that are not launched with EXTRA_INITIAL_ACTIVITY_WIDTH_PX or EXTRA_INITIAL_ACTIVITY_HEIGHT_PX set to their intent.

fun onActivityResized(
    height: @Dimension(unit = 1) Int,
    width: @Dimension(unit = 1) Int,
    extras: Bundle
): Unit

Called when the tab is resized.

fun onMessageChannelReady(extras: Bundle?): Unit

Called when CustomTabsSession has requested a postMessage channel through requestPostMessageChannel and the channel is ready for sending and receiving messages on both ends.

@ExperimentalMinimizationCallback
fun onMinimized(extras: Bundle): Unit

Called when the Custom Tab is minimized by the user such that it covers a small part of the screen.

fun onNavigationEvent(navigationEvent: Int, extras: Bundle?): Unit

To be called when a navigation event happens.

fun onPostMessage(message: String, extras: Bundle?): Unit

Called when a tab controlled by this CustomTabsSession has sent a postMessage. If postMessage() is called from a single thread, then the messages will be posted in the same order. When received on the client side, it is the client's responsibility to preserve the ordering further.

fun onRelationshipValidationResult(
    @CustomTabsService.Relation relation: Int,
    requestedOrigin: Uri,
    result: Boolean,
    extras: Bundle?
): Unit

Called when a relationship validation result is available.

@ExperimentalMinimizationCallback
fun onUnminimized(extras: Bundle): Unit

Called when the Custom Tab is unminimized by the user such that it returns back to its original state.

fun onWarmupCompleted(extras: Bundle): Unit

Called when the browser process finished warming up initiated by warmup.