Skip to content

Move the posture object out of the Screen interface. #67

@darktears

Description

@darktears

Now that the specification only covers the posture it seems weird to have the main entry point of the API to be in the Screen interface.

I strongly think we should move it to another place like window or window.navigator. The thinking is that there is only a single posture at a given time and it's not dependent on the screen.

What does sound best to you folks?

  • window.navigator.posture

  • window.posture which is basically posture

I strongly think that it we land into a generic object like navigator or window we should rename the entry point from posture to device_posture.

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