Thanks for this, being a bit of a novice the “vw” parameter is new to me and I see how it adds a whole new level of control to varying screen sizes. I presume it is efficient to use sparingly?
I’d like to clarify your initial statement though, about responsive setup only functioning when container size becomes smaller. I have to assume you are referring to this specific case as a limitation of responsive setup when applied to button text - otherwise of course ordinary text elements etc will have no such limitation…?
Also just for information in case anybody else at my level of understanding comes across this and needs a few tips -
I found I needed to create the class statement in this way for it to work with the button text
.classname .x-anchor-text-primary {
font-size: calc(13px + 3vw) !important;
}
Within the button definition the “SETUP > Base Font Size” setting will still have an effect on the overall size of the button, but not the text. the “PRIMARY TEXT FORMAT > Font Size” is now overridden.
Out of interest I note that when originally using a standard responsive text definition in the class of the button that " SETUP > Base Font Size" is overridden and “PRIMARY TEXT FORMAT > Font Size” will now control the behaviour of the response. A “px” setting completely overrides the responsive definition. An “em” setting of 1 or lower will have the effect of making the text constantly reduce in size to the responsive defined minimum on expansion or contraction of the container. Conversely the text will constantly increase to the defined maximum on expansion or contraction if set to anything greater than 1em.
I presume this is just a quirky part of the overall dysfunction of the standard responsive text definition with buttons?
Thanks again for pointing me in the right direction.
Andy