TODO: create a very simple component/registration system?

[bkardell]

This gets to the design of the thing we are proposing and how to attack it, but it seems like a system in which you can register a way to determine if it is in a particular modality would allow a single registration/processing point and separate the problem nicely - then keyboard modality would be just the only one we're proposing/have implemented for now - would become easier to evaluate others?

[robdodson]

Can you provide a pseudo code example of what this API would look like? I'm not sure I really grok the purpose.

[bkardell]

The proposal that actually got to the CSSWG punted this to phase two, but the polyfill allows you to add [supports-modality=keyboard] to suggest that this be treated as an element for which the primary modality is 'keyboardy' like inputs rather than not like buttons.

[robdodson]

phase two of custom elements?

[bkardell]

Non specific, just "later" as it would modify the one almost impl from Mozilla that allows it to slip in to l4