We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have a look at this example:
<b:form horizontal="true"> <b:inputTextarea rows="3" placeholder="Username" required="true" label="E-mail:" renderLabel="true" offsetXs="2" labelColXs="2" colXs="6"> <f:facet name="prepend"> <b:icon name="user" /> </f:facet> </b:inputTextarea> <b:inputTextarea rows="3" placeholder="Password" label="Password:" renderLabel="true" offsetXs="2" labelColXs="2" colXs="6"> <f:facet name="prepend"> <b:iconAwesome name="key" /> </f:facet> </b:inputTextarea> </b:form>
What I want is to put an offset of 2 at the begining, and 2 more columns at the end.
The result is the following:
Adding more classes there seems overkill, but the workaround for now is a bit verbose:
<b:form horizontal="true"> <b:row> <b:column offsetXs="2" colXs="8"> <b:inputTextarea rows="3" placeholder="Username" required="true" label="E-mail:" renderLabel="true" labelColXs="2" colXs="10"> <f:facet name="prepend"> <b:icon name="user" /> </f:facet> </b:inputTextarea> </b:column> </b:row> <b:row> <b:column offsetXs="2" colXs="8"> <b:inputTextarea rows="3" placeholder="Password" label="Password:" renderLabel="true" labelColXs="2" colXs="10"> <f:facet name="prepend"> <b:iconAwesome name="key" /> </f:facet> </b:inputTextarea> </b:column> </b:row> </b:form>
I think a better solution should be researched.
The text was updated successfully, but these errors were encountered:
geopossachs
No branches or pull requests
Have a look at this example:
What I want is to put an offset of 2 at the begining, and 2 more columns at the end.
The result is the following:
Adding more classes there seems overkill, but the workaround for now is a bit verbose:
I think a better solution should be researched.
The text was updated successfully, but these errors were encountered: