Closed geopossachs closed 4 years ago
Difficult to say. It's a breaking change. But it's likely that most people expect that behavior.
Is there any antidote if it really breaks the layout of an application?
my workaround in the current version
<b:dropButton value="Ă„nderungen speichern"
look=**"success btn-block"**
col-md="2" offset-md="8"
drop="up" >
Yeah, sure. Mind you, I've already merged your PR. So I wonder what to say to developers who relied on what we consider a bug. However, I suppose we get away with such a breaking change when publishing a new major version such as 1.5.0. It's not exactly semantic versioning, but it's close. :)
if the screen is tall, you won't see anything
currently, if the screen to small, the button is too large
with the bugfix, if the screen to small, the button is well but it exists a button-text cut
i think we need (" btn-block") if the dropButton is used in a grid layout