• I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

Steps to reproduce

• Open demo at https://ant.desig

I am trying to use Select component with accessibility support. It works pretty well except for the usage with FormHelperText . When the select toggle button is focused the screen reader does not read the contents of FormHelperText. I have also tried using the TextField component with select prop for better support as mentioned in [docs](https://material-ui.com/components/selects/#access

Describe the bug
Storybook --host attribute it changes localhost where it should change network host.

start-storybook -h 192.168.89.89 -p 9009
Local:            http://192.168.89.89:9009
On your network:  http://10.0.2.15:9009

The expected result should be like the one bellow

Local:            http://localhost::9009/ 
On your network:  http://192.168.89.89:9009

<Select /> and <DatePicker /> don't offer the option of accessing name, id and other props once the onChange handler triggers. An event object with this information is accessible in the onChange handler for <Input />.

Feature description

Provide access to these variables for Select and DatePicker. It is needed when the component is being passed handler functions from an

Description

The combo box list doesn't have a high enough z-index to overlap other positioned element such as the buttons for another combo box it could be placed above.

The z-index should be increased to make sure it covers non dialog items.

<img width="459" alt="Screenshot 2020-08-03 09 58 02" src="https://user-images.githubusercontent.com/1385752/89196565-01b64f80-d570-11ea-81e8-1

🐛 Bug Report

Currently, the AriaCheckboxGroupItemProps interface extends AriaCheckboxProps and therefore has value?: string. However, i think a checkbox group items actually require setting the value prop, as changing the checkbox group state will not work correctly otherwise(?)

🤔 Expected Behavior

AriaCheckboxGroupItemProps shoud have value: string

😯 Current Behav

One of the consumers of our system uses curly braces for content replacement in strings.

Due to the way that SD currently uses curly braces in the build process there is no way I can have a string that includes the braces for consumption.

I have tried a number of ways to escape the braces with no luck

Other languages and templating systems seem to use the concept of using double curly b