Skip to content

Revise user activation model #1036

@marcoscaceres

Description

@marcoscaceres

This PR brought in new user activation requirement that is a bit "unusual" (unorthodox?):
#1029

We should look at that again and figure out how to do that in a way that integrates better with the platform overall.

(for example, Screen Wake Lock allows re-requesting a lock without permission if the sticky activation was acquired via the API itself - so that achieves the no prompting requirement, while using existing infrastructure).

cc @stephenmcgruer

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions