Container needs to be position: static #18
Conversation
This file contains 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
See what happens if container happens to be position: relativecor anything other than static: http://jsfiddle.net/BdXPL/1/ This could happen if the container has other styles including non-static position. By having the JS overwrite the position, the user can at least know he needs to work around the position and not have to spend half an hour like me trying to see what's fucking up the offset.
|
Try giving the container a width. |
|
Doesn't have an effect. Fork my fiddle and try. |
|
Oh, you meant the elements add the Y offset of the container to their own. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See what happens if container happens to be position: relativecor anything other than static: http://jsfiddle.net/BdXPL/1/
This could happen if the container has other styles including non-static position. By having the JS overwrite the position, the user can at least know he needs to work around the position and not have to spend half an hour like me trying to see what's fucking up the offset.