ui/history/history-page

Classes

HistoryPage

Defined in: app/src/ui/history/history-page.ts:29

The history page: the pages you visited, newest first and grouped by day, with search, and with a way to remove single pages or everything.

Extends

LitElement

Constructors

Constructor

new HistoryPage(): HistoryPage

Defined in: app/src/ui/history/history-page.ts:166

Returns

HistoryPage

Overrides

LitElement.constructor

lifecycle

connectedCallback()

connectedCallback(): void

Defined in: app/src/ui/history/history-page.ts:174

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().

Returns

void

Overrides

LitElement.connectedCallback

Other

bridge

bridge: PageBridge | undefined

Defined in: app/src/ui/history/history-page.ts:162

confirming

confirming: boolean

Defined in: app/src/ui/history/history-page.ts:161

i18n

i18n: Translator | undefined

Defined in: app/src/ui/history/history-page.ts:163

items

items: readonly Item[]

Defined in: app/src/ui/history/history-page.ts:158

more: boolean

Defined in: app/src/ui/history/history-page.ts:160

query

query: string

Defined in: app/src/ui/history/history-page.ts:159

styles

static styles: CSSResult

Defined in: app/src/ui/history/history-page.ts:38

Styles of the page, scoped to its shadow root.

Overrides

LitElement.styles

properties

static properties: object

Defined in: app/src/ui/history/history-page.ts:30

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

confirming: object

confirming.state

state: boolean = true

items

items: object

items.state

state: boolean = true

more: object

more.state

state: boolean = true

query

query: object

query.state

state: boolean = true

Nocollapse

Overrides

LitElement.properties