-
-
Notifications
You must be signed in to change notification settings - Fork 209
fullWidthInput doesn't work for filled, outlined variants #311
Comments
We're having the same issue over here. Does anyone plan on fixing this any time soon? That would really help. |
@mebs If you need this and consider implementing your own chip input, why not start a PR that fixes the issue instead? :-) That sounds like an easier solution to me. |
Hey @leMaik, of course that will be considered! Only problem I see is that it could cause problems with company policy to contribute to open source code but I'd have to double check if it ever comes to that. |
Anyone found a workaround for this issue? |
I added a
|
This issue seems to have been flagged before then marked as fixed but I don't believe the original issue was actually fixed (either that or I found a slightly different issue).
Basically,
fullWidthInput
only works for the standard input variant. The reason is that the standard input variant places the chips as siblings of the input container element, but the outlined and filled variants place the chips inside of the input container element as a startAdornment.Example: https://codesandbox.io/s/nervous-fast-ii9t7?file=/src/App.js
The text was updated successfully, but these errors were encountered: