Fix disabled addVariant call in Tailwind config #2268
Description
@charliepark and I just noticed that this line is not behaving as designed. The comma-separated string thing doesn't seem to be valid for Tailwind, so it is just taking the first one, failing to style disabled inputs. We haven't looked into the scope of this, but I expect fixing it will require at least one or two fixes where we were relying on broken behavior, so we want to do this in a separate PR from #2267 where we noticed this.
Line 74 in ab2939b
To get the logical OR behavior we want, we need to do this:
addVariant('disabled', ['&.visually-disabled', '&:disabled'])(To get logical AND behavior you would put them in the same selector, like &.visually-disabled:disabled.)
I confirmed what the behavior is in the Tailwind playground:
https://play.tailwindcss.com/BZ5FK84yVE?file=config
