Robert Flack

If we target a specific element/layer, I think we could expose a previous transform (e.g. 1/60th of a second ago) which would enable a shader to compute the previous location...

Would it be possible for registered properties to be tracked as a tuple of (name, scope)? Each reference to a property could be based on the scope from which it...

> What made sense to me (as mentioned in the minutes), is that `@property` in shadow-scoped styles makes the property "private" (not inherited from the outer scope), which fixes the...

> > * a shadow tree that wants to register a custom property _for the outer page to use on it_ is _required_ to do so via a global stylesheet,...

Also, if you leave out the `commandfor` attribute, I think reasonable behavior is to scroll the nearest ancestor scroll container to the button.

To summarize the recent discussions, I think the overall direction we're leaning is to define different commands for the directions (4 physical 4 logical), and not to have different distances...

With the scroll command (or the other command invokers) do we have the ability to have an implied disabled state when the command is not feasible. E.g. there is no...

> We can absolutely implicitly set an aria-disabled (I'm assuming you probably still want it to be focusable?) I don't think you do want it to be tab focusable. Every...

> But if I'm currently on the button and it suddenly becomes disabled after activation that's pretty bad right? I think you want tab ordered navigation to proceed from the...

> CSSOM View has some APIs for scrolling. Have you considered extending those? Could you give an example of what you mean by extending those? This is aligning with the...