[typeahead] Set top position #7873
Merged
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
|
LGTM on Chrome 51 on Windows |
|
LGTM on Chrome 52 Mac |
|
LGTM, Chrome 52 and Firefox 45 on Mac. |
elastic-jasper
added a commit
that referenced
this pull request
Jul 28, 2016
--------- **Commit 1:** [typeahead] Set top position * Original sha: dccc3be * Authored by Jonathan Budzenski <jon@jbudz.me> on 2016-07-27T23:07:00Z
elastic-jasper
added a commit
that referenced
this pull request
Jul 28, 2016
--------- **Commit 1:** [typeahead] Set top position * Original sha: dccc3be * Authored by Jonathan Budzenski <jon@jbudz.me> on 2016-07-27T23:07:00Z
jbudz
added a commit
to jbudz/kibana
that referenced
this pull request
Jul 28, 2016
|
Hm, you might want to do |
airow
pushed a commit
to airow/kibana
that referenced
this pull request
Feb 16, 2017
[typeahead] Set top position Former-commit-id: a039064
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.
Currently in Chrome 52+ the absolutely position typeahead box is (correctly?) going to the top left corner of its container and overlapping the search input. This explicitly sets it 32 pixels from the top.
Closes #7801