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

Reproduction link

Steps to reproduce

Project Too Large to isolate

What is exp

The styled and wrapped version of the Next.js Linkcomponent provided by the Material UI next-js template/example is not 100% usable in TypeScript projects because IntelliSense does not work with the current JavaScript version of the component. For example, there are no suggestions available for its props.

I converted the JS

Describe the bug
With multiple pure-documentation MDX docs, the scroll position of the preview window does not reset when switching between docs.

To Reproduce
Steps to reproduce the behavior:

1. Create at least two MDX docs without stories, with content long enough to result in a scroll bar.
2. Select the first doc in the sidebar.
3. Scroll down the first document.
4. Select the

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

<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

🙋 Feature Request

ButtonGroup currently uses the window resize event to figure out whether or not it should switch from horizontal to vertical orientation when there isn't enough room to render all of its buttons (https://github.com/adobe/react-spectrum/blame/main/packages/%40react-spectrum/buttongroup/src/ButtonGroup.tsx#L69-L79). Now that useResizeObserver exists (https://github.com/ado

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