-
-
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
File upload - Original button visible in Chrome latest version #1904
File upload - Original button visible in Chrome latest version #1904
Comments
Ugh it was the bug fix I merged yesterday. I knew something would break. |
Don't think so .. I haven't updated my local version and this shows the same problem. It works ok in FF and IE. |
No, this is very odd. This started after i updated to the latest official Google Chrome v67.0.3396.62 (64bit) without any extensions (released a couple of days ago) on Windows 10. I'll try to do some more debugging. |
This must be a specific Google Chrome on Windows problem. I just installed Chrome on another machine, and the same happens: Update: Is there any specific reason why the |
The file input can't be set to |
It looks like css This will also allow the jquery validation to focus on the element, even tho it is hidden with opacity. This wasn't possible with |
I'm having the same issue. Windows 10 Pro, v1803. Can confirm that adding |
would be nice if this can be added to the 7.2 release. |
This is about Bulma.
it about Bulma
Is it a bug
If it's a bug, is it a browser bug? Yes
This is about the Bulma CSS framework
I'm using Bulma 0.7.1
My browser is: Google Chrome v67.0.3396.62 (win10)
I am sure this issue is not a duplicate? Yes (checked)
Steps to Reproduce
It seams like a bug related to the latest Google Chrome. If you look at https://bulma.io/documentation/form/file/ you'll see that the original upload file button is visible (sass).
Expected behavior
Original form file/upload control should be hidden/invisible.
Actual behavior
Original form file/upload control is visible.
The text was updated successfully, but these errors were encountered: