Re: [w3ctag/design-reviews] Request review of Keyboard Lock (#192)

I wanted to follow-up on some changes that we made in reaction to @cynthia 's comments about naming.

Initially, we opted for naming option (2) `keyboardLock`/`keyboardUnlock` since we thought it would be overkill to have a `navigator.keyboard` object that was only used for locking and unlocking.

However, we are now aware of at least one other API proposal that makes sense to put on a `keyboard` object, so we're switching to (1) creating `navigator.keyboard` and having `lock` and `unlock` methods. This is consistent with the naming of the Screen Orientation API.

I don't believe this is contentious, but I wanted to bring it up in case there are any more comments on the naming. Thanks!

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/192#issuecomment-370103780