-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Placeholder has the same color as the input #2891
Labels
Comments
yes I too face this issue |
This seems to be the case only in Chrome browser. Firefox works fine I believe. |
appsemble-bot
pushed a commit
to appsemble/appsemble
that referenced
this issue
Apr 1, 2020
0.8.1 has an issue where input placeholders have the wrong color. See also: jgthms/bulma#2891
FWIW I encountered this with Safari on MacOS too. |
I've seen this today with Chrome (80.0.3987.149) on macOS. |
jordelver
added a commit
to jordelver/turbo_phoenix
that referenced
this issue
Apr 8, 2020
jordelver
added a commit
to jordelver/turbo_phoenix
that referenced
this issue
Apr 9, 2020
jordelver
added a commit
to jordelver/turbo_phoenix
that referenced
this issue
Apr 14, 2020
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is about Bulma.
Overview of the problem
This is about the Bulma CSS framework
I'm using Bulma version [0.8.1]
My browser is: Chrome
I am sure this issue is not a duplicate?
Description
The placeholder has the exact same color as the input. I'm noob with sass but by debugging a bit it seems that the
rgba($color, $alpha) (
bulmaRgba) is not applied anymore because
$input-coloris not a
color` anymore.I guess this is the culprit
Steps to Reproduce
Visit Bulma homepage, the forms section
Look at any input example.
Expected behavior
Placeholder to be greyed out
Actual behavior
Placeholder is not greyed out
The text was updated successfully, but these errors were encountered: