Intent to Prototype: Handwriting keyword for "touch-action" CSS property

[Chromestatus]

Contact emails

gas...@microsoft.com

Explainer

https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Handwriting/HandwritingIntentCSSValue.md

Specification

https://github.com/w3c/pointerevents/pull/525/files

Summary

This feature introduces a standard that simplifies enabling or disabling handwriting input across multiple platforms. By specifying a new keyword in the touch-action CSS property, developers can now easily indicate whether an element or its subtree should allow handwriting input.

Blink component

UI>Input>Text

Motivation

To disable handwriting input without this feature, developers would need to use preventDefault() on pen touch events, assuming that was an option for the user agent implementation of handwriting input. Android uses a non-standard `touch-action` configuration to disable handwriting input, this proposal will provide a standardized mechanism.

Initial public proposal

https://github.com/w3c/pointerevents/issues/516

TAG review

https://github.com/w3ctag/design-reviews/issues/1018

TAG review status

Issues addressed

Risks

Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Debuggability

None

Is this feature fully tested by web-platform-tests?

No

Flag name on about://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5131558514851840?gate=5146845779853312

This intent message was generated by Chrome Platform Status.