-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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.
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
Search bar not showing full placeholder! #9694
Comments
@aesthytik I'm unable to reproduce this in my machine. This might be different for screens with different resolutions. Would you be interested in fixing this issue and raise a PR for it? |
sure i will do a PR, after fixing it @kakadiadarpan |
I am seeing this using Chrome on Mac. @aesthytik have you been able to find the fix for this? I'm guessing that these are related. |
@tvthatsme yeah that's the same issue! Its not fixed yet |
I can't seem to reproduce the issue too. Strange! |
I have exact same thing as @aesthytik, but only for a short moment, probably the time for the font (FuturaPT) to load (FOUT). Maybe those of you who have the persistent problem are blocking custom fonts? |
@aesthytik I want to work on this issue as this is my first contribution here. May I? |
@yogeshkotadiya I am doing it before and will be opening a PR once @aesthytik replies. You can find more issues. |
Then go for it, You don't have to wait for such a small PR. |
Description
I noticed a little CSS padding problem on placeholder text at search bar
Steps to reproduce
Open the homepage of gatsby.
Expected result
Search placeholder should be visible fully

Actual result
Placeholder not fully shown.
Environment
I am using Ubnuntu 16.04 on google chrome browser
Run
gatsby info --clipboard
in your project directory and paste the output here. Not working? You may need to update your global gatsby-cli -npm install -g gatsby-cli
The text was updated successfully, but these errors were encountered: