Intent to Prototype: HTML handwriting attribute

[Chromestatus]

Contact emails

Adam.Ett...@microsoft.com

Explainer

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

Specification

None

Summary

This feature provides a standard mechanism to indicate whether an element or its subtree should allow user agent handwriting input. User agents that support handwriting recognition as a means to input text using a pen/stylus will behave differently than a user agent that doesn't support handwriting. However, this handwriting may not be desirable for all supported input fields. By specifying the HTML handwriting attribute, authors can indicate when the user agent should not allow handwriting.

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

None

TAG review

None

TAG review status

Pending

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 chrome://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/5186620366782464?gate=5076052179943424

This intent message was generated by Chrome Platform Status.