Skip to content

ui/bookmarks/bookmarks-page

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:32

The bookmarks page: the bookmarks bar and the other bookmarks with their folders. It opens, renames, moves and removes bookmarks, adds folders, and searches all bookmarks.

  • LitElement

new BookmarksPage(): BookmarksPage

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:214

BookmarksPage

LitElement.constructor

connectedCallback(): void

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:224

Invoked when the component is added to the document’s DOM.

In connectedCallback() you should setup tasks that should only occur when the element is connected to the document. The most common of these is adding event listeners to nodes external to the element, like a keydown event handler added to the window.

connectedCallback() {
super.connectedCallback();
addEventListener('keydown', this._handleKeydown);
}

Typically, anything done in connectedCallback() should be undone when the element is disconnected, in disconnectedCallback().

void

LitElement.connectedCallback

disconnectedCallback(): void

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:233

Invoked when the component is removed from the document’s DOM.

This callback is the main signal to the element that it may no longer be used. disconnectedCallback() should ensure that nothing is holding a reference to the element (such as event listeners added to nodes external to the element), so that it is free to be garbage collected.

disconnectedCallback() {
super.disconnectedCallback();
window.removeEventListener('keydown', this._handleKeydown);
}

An element may be re-connected after being disconnected.

void

LitElement.disconnectedCallback

bridge: PageBridge | undefined

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:210

confirming: number | undefined

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:208

editing: number | undefined

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:207

error: string | undefined

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:209

expanded: ReadonlySet<number>

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:206

i18n: Translator | undefined

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:211

items: readonly Item[]

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:204

query: string

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:205

static styles: CSSResult

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:43

Styles of the page, scoped to its shadow root.

LitElement.styles

static properties: object

Defined in: app/src/ui/bookmarks/bookmarks-page.ts:33

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.

confirming: object

state: boolean = true

editing: object

state: boolean = true

error: object

state: boolean = true

expanded: object

state: boolean = true

items: object

state: boolean = true

query: object

state: boolean = true

LitElement.properties