Intent to Prototype: 'step-up' and 'step-down' Invoker Commands

[Chromestatus]

Contact emails

lwa...@igalia.com

Explainer

https://open-ui.org/components/future-invokers.explainer

Specification

No information provided

Summary

Various inputs (e.g. number, range, date) have a mechanism to step up or down their values, via keyboard, AT action, and/or the stepUp() and stepDown() JS functions. The 'step-up' and 'step-down' commands are declarative versions of those functions.

Blink component

Blink>DOM

Web Feature ID

invoker-commands

Motivation

Browsers have built-in number inputs that generally have buttons to increment or decrement the inputs value, but these are hard to style, inconsistent and not always usable on mobile (Chrome is an example of this). By bringing the step up and step down capability to command invokers we enable a declarative way for authors to implement custom versions of these themselves. The ability to use the command button's value attribute as an argument (same way as the JS functions can take an argument) also enables creating buttons that jump the values in larger quantities.

Initial public proposal

https://github.com/openui/open-ui/issues/968

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/476400454

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5077339740438528?gate=5196074446880768

This intent message was generated by Chrome Platform Status.