Skip to content

ui/ui-kit/browser-import

Defined in: app/src/ui/ui-kit/browser-import.ts:46

The import from other browsers, on the settings page and in the setup guide: the browsers found on this computer, what to import, and one button per browser profile.

  • LitElement

new BrowserImport(): BrowserImport

Defined in: app/src/ui/ui-kit/browser-import.ts:132

BrowserImport

LitElement.constructor

bridge: PageBridge | undefined

Defined in: app/src/ui/ui-kit/browser-import.ts:129

enabled: boolean

Defined in: app/src/ui/ui-kit/browser-import.ts:126

i18n: Translator | undefined

Defined in: app/src/ui/ui-kit/browser-import.ts:130

kinds: Readonly<Record<Kind, boolean>>

Defined in: app/src/ui/ui-kit/browser-import.ts:127

outcomes: ReadonlyMap<string, Outcome>

Defined in: app/src/ui/ui-kit/browser-import.ts:128

profiles: readonly Profile[] | undefined

Defined in: app/src/ui/ui-kit/browser-import.ts:125

static styles: CSSResult

Defined in: app/src/ui/ui-kit/browser-import.ts:55

Styles of the list, scoped to its shadow root.

LitElement.styles

static properties: object

Defined in: app/src/ui/ui-kit/browser-import.ts:47

User-supplied object that maps property names to PropertyDeclaration objects containing options for configuring reactive properties. When a reactive property is set the element will update and render.

By default properties are public fields, and as such, they should be considered as primarily settable by element users, either via attribute or the property itself.

Generally, properties that are changed by the element should be private or protected fields and should use the state: true option. Properties marked as state do not reflect from the corresponding attribute

However, sometimes element code does need to set a public property. This should typically only be done in response to user interaction, and an event should be fired informing the user; for example, a checkbox sets its checked property when clicked and fires a changed event. Mutating public properties should typically not be done for non-primitive (object or array) properties. In other cases when an element needs to manage state, a private property set with the state: true option should be used. When needed, state properties can be initialized via public properties to facilitate complex interactions.

enabled: object

state: boolean = true

kinds: object

state: boolean = true

outcomes: object

state: boolean = true

profiles: object

state: boolean = true

LitElement.properties