Add mechanism to control enablement of handwriting
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Summary
A mechanism is being proposed to give developers control over whether handwriting input should be enabled for elements in user agents that support it.
The current proposal suggests adding a new handwriting keyword to the touch-action CSS property to manage this functionality. This GitHub issue aims to gather feedback and perspectives from various relevant working groups, ensuring that all potential implications of this enablement are considered.
This issue will be cross-posted to the pointer events, html and editing working groups to get all the relevant voices involved.
References
- Pointer events WG issue: Contains a better summary of the proposed mechanism.
- CSS handwriting keyword explainer: Explainer that goes into detail on the proposal
- CSS handwriting keyword Chrome Status
See also:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Pointer Events issue and the CSS and HTML handwriting explainers to understand the competing proposals and working-group context. Done would require a settled mechanism and a clearly identified standards change, but this issue currently asks for feedback rather than naming files, tests, or an implementation task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100