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
Elements in inline forms currently stick together as form_row uses spaceless.
form_row
The example of the BS3 documentation shows this:
<form class="form-inline"> <div class="form-group"> <label for="exampleInputName2">Name</label> <input class="form-control" id="exampleInputName2" placeholder="Jane Doe"> </div> <div class="form-group"> <label for="exampleInputEmail2">Email</label> <input type="email" class="form-control" id="exampleInputEmail2" placeholder="[email protected]"> </div> <button type="submit" class="btn btn-default">Send invitation</button> </form>
But is rendered like this (note that widget_form_group_start does not use spaceless):
widget_form_group_start
<form class="form-inline"><div class="form-group"><label for="exampleInputName2"> Name </label><input class="form-control" id="exampleInputName2" placeholder="Jane Doe"></div><div class="form-group"><label for="exampleInputEmail2"> Email </label><input type="email" class="form-control" id="exampleInputEmail2" placeholder="[email protected]"></div><button type="submit" class="btn btn-default">Send invitation</button></form>
But I'm unsure if removing spaceless from form_row might break something else so this might be a bit more complicated.
Ideas?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Elements in inline forms currently stick together as
form_row
uses spaceless.The example of the BS3 documentation shows this:
But is rendered like this (note that
widget_form_group_start
does not use spaceless):But I'm unsure if removing spaceless from
form_row
might break something else so this might be a bit more complicated.Ideas?
The text was updated successfully, but these errors were encountered: