Fix css regression for has_one and has_many nested form#2337
Merged
mshibuya merged 1 commit intoJun 30, 2015
Conversation
Contributor
|
Well done! Looks good to me! |
Contributor
|
dalpo
force-pushed
the
feature/fix-has-many-markup
branch
from
420e277 to
28e5e3e
Compare
Contributor
Author
|
Update: |
mshibuya
added a commit
that referenced
this pull request
Jun 30, 2015
Fix css regression for has_one and has_many nested form
Member
|
Thanks! 😸 |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-establish the margin below the has_may/has_one button as the boostrap2 version
Before
After