Add keyboard lock (harmful).

[dbaron]

This adds it as a harmful position, although it could also be written as
a defer position based on the feedback in #196.

Closes #196.

[tantek]

Agreed. The UX concerns noted in Issue #196 are sufficient to mark the current proposal as harmful. Significant changes to address those concerns would be sufficient to bring this back for re-evaluation.

[bholley]

We're doing some thinking about the right way to approach this API and the associated use-cases, will circle back.

[martinthomson]

To be more clear about this, we think that this is a reasonable use case, but it might be a poor implementation of that use case. It might be better to defer for now.

[adamroach]

To be more clear about this, we think that this is a reasonable use case, but it might be a poor implementation of that use case. It might be better to defer for now.

I'm pretty hesitant to take the "good use case, harmful proposal" situation and call it anything other than harmful. Most of our "harmful" designations could be described that way. We've seen other positions in this repository construed completely without nuance in other venues, so I think it's important that we mark things clearly as "harmful" if the currently written-down mechanism is harmful.

[tantek]

This: "mark things clearly as "harmful" if the currently written-down mechanism is harmful".

IMO merge it. It's worth getting on the record the current state, regardless of what the potential state might be in some theoretical optimistic future.

[adamroach]

This text looks good. Ship it.

[martinthomson]

The team that is responsible for this has this on their backlog; let's hold this until we collect their input.