Skip to content
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

no-drop cursor state on date-picker input field #161

Closed
rocketpunch opened this issue Jun 28, 2013 · 4 comments
Closed

no-drop cursor state on date-picker input field #161

rocketpunch opened this issue Jun 28, 2013 · 4 comments

Comments

@rocketpunch
Copy link

Hello, i'm trying to use this script on a bootstrap page. When i hover on the input field for the date-picker i get the no-drop (forbidden action icon) cursor. Is there a way to remove this effect?
Also the date picker is not closing itself after the date is selected, i have to click outside to close it.
I already tried commenting out other .js scripts to no avail so it shouldn't be a conflict issue.
Browsers tested are Firefox 22 and Chrome 27.0.1453.116
thanks for your help-

@brunogaspar
Copy link

For the cursor thing, you can create a new css class and apply that class to those inputs, something like this

.myclass {
    cursor: pointer;
    background: #ffffff;
}

The other one, is related to this issue here #160 i added a comment aswell saying how you can remove the focus after you select a date/time, hope it helps.

@amsul amsul closed this as completed in 051ec1f Jun 28, 2013
@rocketpunch
Copy link
Author

ok thanks but i was more interested in nailing what's causing this behaviour in the script. overriding with css removes the symptom but not the cause.

@amsul
Copy link
Owner

amsul commented Jun 29, 2013

Sorry for the lack of explanation. In order to disable virtual keyboards from popping up when focusing onto the input element, the element receives a disabled attribute. This causes the pointer on some browsers to behave that way.

Hope that clarifies things.

@rocketpunch
Copy link
Author

thanks, now it makes sense, i'll use the css fix as suggested by brunogaspar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants