@rfbotto I think the preferred route of deprecation, is to first display warnings when the deprecated prop is used and then in the next major version (v4) to remove them.

That's a good point @joshwooding, didn't think of it. Then it should be fine to keep this PR open and only merge it into the next major version and in the meantime create a PR with the deprecation warning for those props (in case the solution in this PR gets accepted).

The deprecation path looks great, well done 👌 !

Nice. But I have some problem with this latest update.

My tab will use fullWidth in mobile and using default in Desktop.

Before this. It's very easy.

const {classes, fullScreen} = this.props

<Tabs fullWidth={fullScreen}
...

export default withStyles(styles)(withMobileDialog()(Module))

This latest update make my code become messy because variant props only accept 2 string.. Perhaps having a default value to set back to tabs behavior to default behavior is appreciated. 😺

Hi, I have to disagree with this change.
We are using scrollable and fullWidth together just fine, it only requires adding a minWidth to the Tab button components but otherwise it works just fine.
This is a breaking change for our layout - could this be reverted / are there other solutions to keep fullWidth and scrollable available at the same time?