Runar reported challenges when trying to set the size of the input component in Vue which is being ignored.
"An issue with f-input is that the size attribute is ignored due to width: 100%" - Runar
Interim solution has been to patch the Vue component:
"v0.11.0 supports input-wrapper-class as a prop on f-input - so then you can do w-1/4 to control just the input element wrapper" - Dave
This is a CSS issue and has to do with how we're structuring the relative/absolute positioning
We either need a rethink our CSS structure, or we could throw up a concrete "we don't support this HTML attribute (size), but here's what you can do instead" - just depends on how we want to approach this
The ideal solution would gracefully (backward compatible) rework our input element classes so we can support both size and width changes to the input element - while maintaining the correct position of the prefix/suffix and other decorative shit that happens with the input field
Defn of Done
Land approach to handling this, either rework CSS in a backwards compatible way OR decide to not support size attribute on inputs
If we decide to rework, add support to input in a backwards compatible way
If we decide to not support the size attribute, document alternative solution
Background
Runar reported challenges when trying to set the size of the input component in Vue which is being ignored. "An issue with f-input is that the size attribute is ignored due to width: 100%" - Runar
Interim solution has been to patch the Vue component: "v0.11.0 supports input-wrapper-class as a prop on f-input - so then you can do w-1/4 to control just the input element wrapper" - Dave
This is a CSS issue and has to do with how we're structuring the relative/absolute positioning
Conversation ref on slack here: https://sch-chat.slack.com/archives/C01GYKPJVFT/p1646253864034579
Task
We either need a rethink our CSS structure, or we could throw up a concrete "we don't support this HTML attribute (size), but here's what you can do instead" - just depends on how we want to approach this
The ideal solution would gracefully (backward compatible) rework our input element classes so we can support both size and width changes to the input element - while maintaining the correct position of the prefix/suffix and other decorative shit that happens with the input field
Defn of Done