I'm trying to create a simple hover tooltip component and its proving to be impossible. A box displays on hover with text, where it should size properly based on text length with appropriate padding, which works until you try to create a reusable component. So I would need a new component for each phrase, completely defeating the benefit of a component. How are people building design systems without this functionality on buttons?
Am I missing something here?
Why won't Boxes work in Components?
Why won't Boxes work in Components?
Where am I?
In UXPin you can ask and answer questions and share your experience with others!
Can you make a video of this, giving an exact idea?
See gif. I'd like to be able to have a component where I can change the icon and text per use. The box behind the text should change size based on text length. I want a component so I have the option to globally change font or bg opacity or color, or circle size/shape, etc.
Do you mean the elastic box feature?
This is not available for boxes and buttons that are/are in component
https://www.uxpin.com/docs/editor/elements/#box
Yes, thank you for replying.
I am aware elastic boxes will not work in component. I'm trying to understand why. It is basically impossible to build a true design system without that feature.
I see your point. Thanks for the insight
This was a direct product decision.
We have this feature request logged on our end, hopefully, this can be improved in the future.
Yeah man. I cann feel you! I found that very hard way.
Completely agree this needs to be implemented. It's the first thing I tried after signing up. Elastic boxes are the most basic building blocks for websites / applications. How can you advertise all this stuff about design systems and not even have elastic buttons as a component?! Bit disappointed folks.
Ran into this today and it looks like this is a problem that has been reported a lot, yet not implemented, for over a year.
Components that lack at least width override capabilities, defeat the purpose of Components. Not every button in an app is going to be exactly the same width, because of text, plus often you want your buttons to fill its container. Really, filling to a container is 90% of design on the web. lol.
"Break from Component" is just about as good as copy-pasting across the app. And what good is a design system, if the prototypes in the tool, can't adhere to the design system created in the tool?
There are some cool features I wish other things had, but not at the expense of all actual consistency.