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.

Sign up for GitHub

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

Jump to bottom

describe principles for naming of locking/unlocking APIs #85

Open

dbaron opened this issue Feb 1, 2018 · 1 comment

Assignees

Labels

Status: In Progress Topic: JS Topic: Naming

Milestone

2021-03-01-week

Member

dbaron commented Feb 1, 2018

Starting from w3ctag/design-reviews#192 (comment) we had some discussion of naming of locking/unlocking APIs. This may also be related to w3ctag/design-reviews#217 .

We should probably document the principles for naming and ergonomics of locking/unlocking APIs, given the number of patterns we've observed already.

garykac commented Mar 3, 2018

I just added a comment about the naming of the Keyboard Lock API.
w3ctag/design-reviews#192 (comment)

Basically, we're modeling it after the Screen Orientation API and having a object navigator.keyboard with lock and unlock methods.

torgo assigned cynthia

torgo added Status: Consensus to write Status: In Progress and removed Status: Consensus to write labels

plinss added this to the 2021-02-01-week milestone

LeaVerou added Topic: Naming Topic: JS labels

plinss modified the milestones: 2021-02-01-week, 2021-03-01-week

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment