-
Notifications
You must be signed in to change notification settings - Fork 169
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
Date can still be changed in readonly mode #133
Comments
This is as designed - it merely passes on the attribute. I'd be welcoming a
PR for docs clarification and/or for a bound 'disabled' attribute - ideally
named so that it doesn't conflict with existing HTML attributes.
…On Fri, 17 Feb 2017, 16:05 Ahmet Emre Kılınç, ***@***.***> wrote:
If readonly is set true, the input text cannot be changed, however onclick
date can still be changed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#133>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AAoow-RHAU9oJ5YCqek9l7R7jizUj8u-ks5rdbdGgaJpZM4MEXwo>
.
|
Is that design choice documented somewhere? I couldn't find it in the Pikaday readme. Having a datepicker on a read-only field (especially as it can still change the displayed input value) doesn't make any sense to me. Please enlighten me. |
There's also a workaround in that thread, which I've adapted to ember-pikaday for my needs. I'm already extending the component, but if you don't want to extend, I haven't tested this, but you may be able to accomplish this with
|
Thank you for your response! I've stopped working with Ember but I'm sure this will help someone. |
If readonly is set true, the input text cannot be changed, however onclick date can still be changed.
The text was updated successfully, but these errors were encountered: