[Tabs] Tabs doesn't work with Tab as a custom component

[w3lld1]

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Tabs doesn't switch between Tab if it's a custom component that returns Tab

Expected Behavior 🤔

The same behavior as with Tab

Steps to Reproduce 🕹

You can see this behavior here

Steps:

1. Create component that returns Tab
2. Use it in Tabs instead of Tab

[eps1lon]

It doesn't look like this bug report has enough info for one of us to reproduce it.

Please provide a CodeSandbox (https://material-ui.com/r/issue-template-next), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.

Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

[w3lld1]

It doesn't look like this bug report has enough info for one of us to reproduce it.

Please provide a CodeSandbox (https://material-ui.com/r/issue-template-next), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.

Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

I provided codesandbox example in my first message. Sorry if it wasn't noticeable.

Duplicate here:
https://codesandbox.io/s/material-demo-forked-vo6zv

[eps1lon]

I provided codesandbox example in my first message. Sorry if it wasn't noticeable.

My bad, sorry.

I checked the codesandbox and the issue is that props aren't spread to the actual Tab component like so:

-function CustomTab({ value }) {
-  return <Tab value={value} label={value} />;
+function CustomTab({ value, ...props }) {
+  return <Tab value={value} label={value} {...props} />;
}

Leaving this open since this is probably something we want to investigate for our experimental Tab API or at least provide a runtime warning.

[ChristopherChudzicki]

This recently bit us and tabs appeared function since they were links. However, they weren't functional for keyboard users.

I might have missed it, but is this spreading requirement mentioned anywhere in the docs? Until a runtime warning becomes available, a callout in the docs might be helpful.