Sent when the "Start Browsing" button has been clicked.
Sent when onboarding is complete and the user has chosen to go to settings
Sends an initial message to the native layer. This is the opportunity for the native layer to provide the initial state of the application or any configuration, for example:
{
"stepDefinitions": {
"systemSettings": {
"rows": ["dock", "import", "default-browser"]
}
},
"order": "v2",
"exclude": ["dockSingle"],
"locale": "en"
}
In that example, the native layer is providing the list of rows that should be shown in the
systemSettings step, overriding the default list provided in data.js
.
This will be sent if the application fails to load.
This will be sent if the application has loaded, but a client-side error has occurred that cannot be recovered from
Sent when the user wants to keep the application in the dock/taskbar.
Native side should respond when the operation is 'complete'.
Sent when the user wants to import data. The UI will remain in a loading state until the native layer sends a response.
Native side should respond when the operation is 'complete'.
Sent when the user wants to set DuckDuckGo as their default browser. The UI will remain in a loading state until the native layer sends a response.
Native side should respond when the operation is 'complete'.
Sent when the user wants to enable or disable the bookmarks bar
Sent when the user wants to enable or disable the session restore setting
Sent when the user wants to enable or disable the home button Note: Although the home button can placed in multiple places in the browser taskbar, this application will only ever send enabled/disabled to the native layer
Sends a notification to the native layer that the user has completed a step
This describes the messages that will be sent to the native layer,