Skip to content

Keyboard Lock #182

Open
0 of 1 issue completed
Open

Description

@philn

WebKittens

No response

Title of the spec

Keyboard Lock

URL to the spec

https://wicg.github.io/keyboard-lock/

URL to the spec's repository

https://github.com/wicg/keyboard-lock/

Issue Tracker URL

No response

Explainer URL

https://github.com/WICG/keyboard-lock/blob/gh-pages/explainer.md

TAG Design Review URL

No response

Mozilla standards-positions issue URL

mozilla/standards-positions#196

WebKit Bugzilla URL

No response

Radar URL

No response

Description

This spec can be useful in cloud gaming use-cases for instance. I'd like to know Apple's position about supporting this spec in WebKit.

Activity

  1. added
    venue: WICGProposal is incubated in the Web Incubator Community Group
    from: GoogleProposed, edited, or co-edited by Google.
    on May 2, 2023
  2. moved this from Unscreened to Needs position in Standards Positions Review Backlogon May 2, 2023
  3. annevk commented on May 4, 2023

    @annevk
    Contributor

    Is this being maintained? E.g., WICG/keyboard-lock#58 (something I was wondering about as well) from 2020 is still open.

  4. changed the title [-]Keyboard: `lock()`[/-] [+]Keyboard Lock[/+] on May 4, 2023
  5. added
    concerns: compatibilityThis proposal may create a compatibility risk for existing sites
    concerns: internationalizationThis proposal doesn't sufficiently account for different languages or locales
    concerns: securityThis proposal may cause security risk if implemented
    concerns: integrationCan't be used w/ other web platform features (or unclear what happens if used together)
    concerns: portabilityThis proposal may be impossible or difficult to implement on at least one important platform
    concerns: API designThe API for this is error-prone, poorly named, or inconsistent with the platform
    concerns: annoyanceThe technology described in this proposal could be used to do things that may annoy the user
    on May 5, 2023
  6. 7 remaining items

  7. tomayac commented on Oct 5, 2023

    @tomayac

    It would be great to get WebKit's support for this feature, since it can make fullscreen experiences a lot better: https://developer.chrome.com/blog/better-full-screen-mode/.

  8. annevk commented on Oct 5, 2023

    @annevk
    Contributor

    @tomayac I think that would require someone to step up and deal with the feedback that has been given. I see I filed issues in 2017 that still haven't been resolved.

  9. jesup commented on Nov 4, 2023

    @jesup

    It looks like no real work has been done (and hardly any comments) to any of the issues filed against this over 3 years ago. It has the appearance of a post-facto spec thrown over the wall after an implementation was done, and then dropped.

  10. philn commented on Nov 4, 2023

    @philn
    MemberAuthor

    Hi @philn, just pinging for an update. If we don't hear back we might mark this as "withdrawn"?

    Feel free to do that yes.

  11. xingri commented on Nov 14, 2023

    @xingri

    @philn @marcoscaceres Per the discussion with @annevk on the last WebKit Contributors meeting,
    I believe it is still worth to try implementing it based on the current spec draft under the flag.
    I filed a bug for implementing this feature. (CC: @jdatapple , @stwrt)

  12. marcoscaceres commented on Nov 23, 2023

    @marcoscaceres
    Contributor

    Sure, but we should fix the spec in parallel too if we can. Otherwise, it may not be possible to unflag this generally given all the issues we've identified (and a lot of code and tests may need to be re-written).

    @tomayac, can you check on your side if there is resourcing to collaborate on fixing the API? It's not in a good state and we collaborate on something better.

  13. xingri commented on Nov 27, 2023

    @xingri

    @marcoscaceres Sure. We also think the enhancement(or clarification) in the specification is needed. We will make sure what it needs to be improved while preparing a draft implementation for the more in-depth discussion of the spec.

  14. marcoscaceres commented on Nov 29, 2023

    @marcoscaceres
    Contributor

    Right, but please don't do that in isolation (we should agree on a design and see if we can get everyone on board). If we need have a call, let's set one up. I'm worried that you will end up implementing a bunch of stuff that we won't be able to land - or you'll end up shipping a design that no one is really happy with, which will confuse developers and the ecosystem.

  15. xingri commented on Nov 29, 2023

    @xingri

    @marcoscaceres Sounds great! Will get back to you soon.

  16. marcoscaceres commented on Nov 29, 2023

    @marcoscaceres
    Contributor

    Mozilla has an interesting proposal that seems to address a lot of the concerns we raised above. I asked if they are willing to bring it over to the WICG.

    Just to be clear, Mozilla proposes just having this as an option when calling .requestFullscreen(), which makes a lot of sense. It also tries to solve for the potential key combination foot guns.

    It also makes the API super simple: it reduces the whole thing down to a single dictionary member, which is really elegant.

  17. xingri commented on Nov 29, 2023

    @xingri

    @marcoscaceres The Mozilla proposal looks good to me but we will review internally and share the feedback.

  18. jrmuizel commented on Oct 23, 2024

    @jrmuizel

    @marcoscaceres given WebKit/WebKit#21374 has landed does WebKit have an updated standards position?

  19. self-assigned this
    on Apr 19, 2025
  20. rik commented on Dec 3, 2025

    @rik

    Given an implementation has been enabled by default, it seems a position has been reached. My understanding is that it's implementing the proposal listed in #481.

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

Metadata

Metadata

Labels

concerns: API designThe API for this is error-prone, poorly named, or inconsistent with the platformconcerns: accessibilityThere might be accessibility issues with the proposal.concerns: annoyanceThe technology described in this proposal could be used to do things that may annoy the userconcerns: compatibilityThis proposal may create a compatibility risk for existing sitesconcerns: dependenciesSome of this proposal's dependencies are unstable, immature, or lack widespread support.concerns: device independenceProposal is hardware- or OS-specific, in a way that may risk the device independence of the Webconcerns: integrationCan't be used w/ other web platform features (or unclear what happens if used together)concerns: internationalizationThis proposal doesn't sufficiently account for different languages or localesconcerns: portabilityThis proposal may be impossible or difficult to implement on at least one important platformconcerns: securityThis proposal may cause security risk if implementedfrom: GoogleProposed, edited, or co-edited by Google.venue: WICGProposal is incubated in the Web Incubator Community Group

Type

No type

Projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

⌂ 换网址