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

Make DateInputWidget use a simple text field (Pylons/deform#101) #114

Closed
wants to merge 1 commit into from

Conversation

rbu
Copy link
Contributor

@rbu rbu commented Aug 28, 2012

input[type=date] is now supported by modern browsers and displays a
native date picker. This makes sense for a native widget, but opens two
datepickers when the jquery UI datepicker is added. Revert to type=text
for now.

input[type=date] is now supported by modern browsers and displays a
native date picker. This makes sense for a native widget, but opens two
datepickers when the jquery UI datepicker is added. Revert to type=text
for now.
@rbu
Copy link
Contributor Author

rbu commented Aug 28, 2012

issue #101

@kiorky
Copy link
Member

kiorky commented Sep 21, 2012

Maybe it would be better to fix the original issue ?

@tonthon
Copy link
Contributor

tonthon commented Sep 21, 2012

Note : The jquery datepicker allows much more customisation than the browser's widget (through the altField).

@rbu
Copy link
Contributor Author

rbu commented Nov 7, 2012

@kiorky, the only way I know of to avoid using the native date picker in modern browsers is not to use input[type=date]. What do you mean by original issue? My patch makes this a "no native" date input, the other solutions I see are making it a "native only" input that has no fancyness in old browsers or making it a "native, if available" input which requires support from the jQuery UI datepicker and has its own problems (such as users seeing different pickers ond different devices).
There could be an option for a deform user to choose between these, and the patch simply provides the first choice.

@ppaez
Copy link
Member

ppaez commented Mar 20, 2013

The solution in pull request #142 was merged.

@ppaez ppaez closed this Mar 20, 2013
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

Successfully merging this pull request may close these issues.

4 participants