Skip to content

Local storage trigger is never read from saved UI settings #17

Description

@webJose

Problem

The ui.localStorageTrigger UI option is currently being persisted in local storage as part of the user interface settings, but the code that triggers the user interface doesn't look at this saved value, which is confusing at the very least.

Proposal

To move the localStorageTrigger option up in the hierarchy, so it is no longer saved and becomes a factory function option instead. Factory functions (currently shadowDom and base) are not persisted to local storage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions