Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Select: help/error is positioned to whichever parent element has position relative #436

Closed
Radek-Palisa opened this issue Oct 7, 2018 · 1 comment
Closed

Select: help/error is positioned to whichever parent element has position relative #436

Radek-Palisa opened this issue Oct 7, 2018 · 1 comment
Assignees
@vepor
Labels
Bug Something isn't working

Comments

@Radek-Palisa
Copy link

Expected Behavior

Help/error to be underneath the input field.

Current Behavior

help/error is now placed to the first parent element that has position relative on itself.

image

Possible Solution

  1. Remove position absolute

or

  1. put position relative on label, but then also include margin-bottom on the label so that the element underneath is not overlapping with the help/error

Context (Environment)

using Orbit 0.13.0
@vepor vepor added Bug Something isn't working process/requested-changes labels Oct 8, 2018
@vepor
Copy link
Contributor

vepor commented Oct 9, 2018

@Radek-Palisa did you mean Select component?

@vepor vepor changed the title <InputField />: help/error is positioned to whichever parent element has position relative Select: help/error is positioned to whichever parent element has position relative Oct 9, 2018
@vepor vepor self-assigned this Oct 9, 2018
@vepor vepor mentioned this issue Oct 9, 2018
Merged
@tomashapl tomashapl mentioned this issue Oct 9, 2018
Merged
@vepor vepor removed the processing label Oct 17, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vepor vepor

Labels
Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vepor @Radek-Palisa