[RFC] Provide merged props and state to Styles and Accessibility

[microsoft]

[RFC] Provide merged props and state to Styles and Accessibility

[levithomason]

Problem 👍
Proposed solutions 1 and 2 👍

As for the style function argument, even though props was popularized by React it seems many CSS in JS libraries call this argument props, even if they aren't supporting React. Some also call it state, as CSS in JS is also described as "styles as a function of state."

I think we should look around at the ecosystem and make a determination based on what is emerging and stay away from inventing anything new. Here are a few popular libraries

https://github.com/Khan/aphrodite
https://github.com/paypal/glamorous
https://github.com/FormidableLabs/radium
https://emotion.sh/
https://github.com/cssinjs/jss
http://fela.js.org/
https://github.com/styled-components/styled-components
https://github.com/styled-components/polished
https://github.com/styletron/styletron

Even more are listed here here:

https://github.com/MicheleBertoli/css-in-js

[kuzhelov]

required functionality is now introduced, let's spend some time to figure out if something needs to be changed for the name of props - based on the experience of other libs (totally agree that we'd better to stick to commonly taken approach).

[hughreeling]

Perhaps also do #176

[kuzhelov]

this one is addressed by #173, closing