Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardizing managed user agent behavior #65

Open
reillyeon opened this issue Sep 1, 2023 · 0 comments
Open

Standardizing managed user agent behavior #65

reillyeon opened this issue Sep 1, 2023 · 0 comments
Labels
session Breakout session proposal

Comments

@reillyeon
Copy link
Member

reillyeon commented Sep 1, 2023

Session description

Most popular user agents support “enterprise management” features which gives device owners control over the user agent. These features can modify the user-facing behavior of the user agent, such as by automatically configuring bookmarks or the home page, or by disabling features such as integrated developer tools. They may also affect web-exposed behavior of the user agent such as by automatically granting or denying permissions. Recent incubations have also proposed new APIs which would only be exposed to sites when running on a managed browser.

Session goal

Explore how to approach standardization when these management features have web-exposed behavior.

Additional session chairs (Optional)

@jyasskin

IRC channel (Optional)

#managed-user-agents

Who can attend

Anyone may attend (Default)

Session duration

60 minutes (Default)

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Estimated number of in-person attendees

Don't know (Default)

Instructions for meeting planners (Optional)

No response

Agenda, minutes, slides, etc. (Optional)

@reillyeon reillyeon added the session Breakout session proposal label Sep 1, 2023
This was referenced Sep 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
session Breakout session proposal
Projects
Status: No status
Development

No branches or pull requests

1 participant