Skip to content

Persist state between reloads/refreshes #67

@mrxz

Description

@mrxz

With the 1.x version of the extension the state of the emulated headset and controllers was retained in the dev tool panel. This meant that after reloading the tab, the input sources were at the same location as before. This was convenient as you'd only have to move and orientate the headset and input sources once when testing a specific setup.

In the new 2.0 version every refresh of a page, the state is back to the default. It would be nice if the state was persisted. Possibly using sessionStorage as that survives reloads but does not persist beyond a (testing/debugging) session when opening the same page in a different tab or at a later point.

Creating this feature request in this repo, but it might make sense to implement the relevant logic somewhere in the immersive-web-emulator-runtime instead of the extension.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions