I really need to figure out how to make the button background responsive according to the characters of text inside the button. Is it not a good idea to have this on the roadmap for button option?
I can’t seem to find the part of the HTML which I need for my project as there is a long list of HTML text for css and fonts. Would hope someone can point out a specific solution.
It looks like the HTML in the Page header in the AirDev example no longer modifies the HTML elements in the RG cell (might be a Bubble bug since that worked previously). For now, I put the code in the HTML element here:
Thankyou for taking the time to explain your answer.
I understand your creative workaround but im still wondering why Bubble has not made the button background responsive or some kind of setting which we could select so that the button is automatically responsive and floating to the right or center of a group its placed in.
No problem! I’m not sure if it’s something that Bubble has planned for the future. I think something similar could be created by a plugin developer to make it easier for people to use and modify the styling, without needing to use the HTML element.
@nocodeventure The elements are not responsive in width themselves, but the HTML styling in this example creates that “chat Bubble” effect so the background color only stretches as far as the text. This works in a vertical RG, but would not look good if the elements were in a horizontal rg. If you were to place the elements side-by-side, the elements themselves would have the same width at all times (as defined in the editor), but the styling would make them look like bubbles. My thought was that it would be possible to create a plugin which accomplishes the chat bubble effect as well, to make it easier for Bubblers to add that element to an RG, modify the font, background color, size, etc. (Neither would have an actual responsive width, it would just have the chat Bubble effect.) My apologies for any confusion!
@mike_verbruggen Thank you for fixing that! Originally it was in the page header of the AirDev example where the styling modified two divs in their messaging example, so I think that’s why it had those sections. (I know basically zero code and wasn’t sure what else to take out). Will update the demo shortly with the correct version you have!