Constructor Detail

Method Detail

• chain

   abstract BrowseEventHandlers chain(BrowseEventHandlers other)

  Chain the other browse event handler to the tail of this one.

• getOnWillLaunchBrowser

   abstract WebPageEventHandler getOnWillLaunchBrowser()

  Fire when the browser is about to be launched.

• getOnBrowserLaunched

   abstract WebPageWebDriverEventHandler getOnBrowserLaunched()

  Fire when the browser is launched.

• getOnWillFetch

   abstract WebPageWebDriverEventHandler getOnWillFetch()

  Fire when the url is about to be fetched.

• getOnFetched

   abstract WebPageWebDriverEventHandler getOnFetched()

  Fire when the url is fetched.

• getOnWillNavigate

   abstract WebPageWebDriverEventHandler getOnWillNavigate()

  Fire when the url is about to be navigated.

• getOnNavigated

   abstract WebPageWebDriverEventHandler getOnNavigated()

  Fire when the url is navigated, just like we clicked the Go button on the browser's navigation bar.

• getOnWillInteract

   abstract WebPageWebDriverEventHandler getOnWillInteract()

  Fire when the interaction with the webpage is about to begin.

• getOnDidInteract

   abstract WebPageWebDriverEventHandler getOnDidInteract()

  Fire when the interactions with the webpage have been completed. This event is fired after the interactions are completed, such as clicking a button, filling a form, and so on.

  This event is fired after the completion of the following actions:

  • Checking the document state

  • Completing webpage scrolling

  • Computing webpage features

  The event is fired before the following actions:

  • Stopping the browser tab

• getOnWillCheckDocumentState

   abstract WebPageWebDriverEventHandler getOnWillCheckDocumentState()

  Fire when the document state is about to be checked.

• getOnDocumentActuallyReady

   abstract WebPageWebDriverEventHandler getOnDocumentActuallyReady()

  Fire when the document is actually ready. The actuallyReady state is determined using an algorithm that is executed within the browser.

  This actuallyReady state differs from the standard Document.readyState, which describes the loading state of the document. When Document.readyState changes, a readystatechange event fires on the document object.

• getOnWillScroll

   abstract WebPageWebDriverEventHandler getOnWillScroll()

  Fire when we are about to perform scrolling on the page.

• getOnDidScroll

   abstract WebPageWebDriverEventHandler getOnDidScroll()

  Fire when we have performed scrolling on the page.

• getOnDocumentSteady

   abstract WebPageWebDriverEventHandler getOnDocumentSteady()

  Fire when we have performed scrolling on the page, at which point the document is considered not to change unless other interactive actions occur. It is a good time to perform custom actions.

  Custom actions are defined by the user using code snippets that are written for a specific purpose, such as clicking a button, filling a form, and so on.

  The event is fired after the completion of the following actions: onDocumentActuallyReady, onWillScroll, onDidScroll

  The event is fired before the following actions: onWillComputeFeature, onFeatureComputed, onDidInteract, onWillStopTab, onTabStopped

• getOnWillComputeFeature

   abstract WebPageWebDriverEventHandler getOnWillComputeFeature()

  Fire when the webpage features are about to be computed.

• getOnFeatureComputed

   abstract WebPageWebDriverEventHandler getOnFeatureComputed()

  Fire when the webpage features have been computed.

• getOnWillStopTab

   abstract WebPageWebDriverEventHandler getOnWillStopTab()

  Fire when the browser tab is about to be stopped.

  This event is fired after the completion of the following actions:

  • Checking the document state

  • Completing webpage scrolling

  • Computing webpage features

  • Interacting with the webpage

• getOnTabStopped

   abstract WebPageWebDriverEventHandler getOnTabStopped()

  Fire when the browser tab is stopped.