[w3c/editing] Add mechanism to control enablement of handwriting (Issue #472)

# 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](https://github.com/w3c/pointerevents/issues/516): Contains a better summary of the proposed mechanism.
- [CSS handwriting keyword explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Handwriting/HandwritingIntentCSSValue.md): Explainer that goes into detail on the proposal
- [CSS handwriting keyword Chrome Status](https://chromestatus.com/feature/5131558514851840)

# See also:

- [HTML handwriting attribute explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Handwriting/explainer.md)
- [HTML handwriting attribute Chrome Status](https://chromestatus.com/feature/5186620366782464)
- [HTML handwriting attribute Intent to Prototype](https://groups.google.com/a/chromium.org/g/blink-dev/c/0r_tV6k0NyA)
- [Enable direct pen and touch to have different touch-action behavior](https://github.com/w3c/pointerevents/issues/203)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/472
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/472@github.com>

Received on Wednesday, 27 November 2024 18:15:51 UTC