Anyway, we could take in consideration the button alternative that, in my
opinion, is more flexible. I mean that the calendar popup should be shown
when the user clicks a button near the control and not when the control is
focused. In this way the autocomplete browser feature (that, in some
scenarios, could be useful) will be preserved and, from a developer point
of view, it's simpler remove a button or change its onclick action when
he/she want use an other calendar or even use the html5 calendar feature.
Il giorno venerdì 19 luglio 2013 15:13:25 UTC+2, Paolo Caruccio ha scritto:
>
> We could also change web2py.js
>
> Attached the file modified.
>
> Il giorno venerdì 19 luglio 2013 10:40:44 UTC+2, Massimo Di Pierro ha
> scritto:
>>
>> How about we put this in web2py,js?
>>
>> jQuery('input.date,input.datetime,input.time').attr('autocomplete','off')
>>
>> Massimo
>>
>> On Thursday, 18 July 2013 17:11:19 UTC-5, Paolo Caruccio wrote:
>>>
>>> I don't think so but you could set the autocomplete attribute of date
>>> inputs in your form to off by adding in the related controller:
>>>
>>> inp_dates = form.elements('input', _class='date')
>>> for inp_date in inp_dates:
>>> inp_date['_autocomplete'] = 'off'
>>>
>>>
>>>
>>> Il giorno giovedì 18 luglio 2013 23:42:21 UTC+2, Jim S ha scritto:
>>>>
>>>> So it should be an update to the widget, right?
>>>>
>>>> -Jim
>>>>
>>>>
>>>> On Thu, Jul 18, 2013 at 4:24 PM, Paolo Caruccio
>>>> <paolo.ca...@gmail.com>wrote:
>>>>
>>>>> Well, the automplete is a <form> | <input> attribute and therefore you
>>>>> could set in HTML code
>>>>>
>>>>> <form name="form1" id="form1" method="post" autocomplete="off" action
>>>>> =""> ... </form>
>>>>>
>>>>> or
>>>>>
>>>>> <input type="text" name="myfield" autocomplete="off">
>>>>>
>>>>> w3c documentation:
>>>>>
>>>>> for the form
>>>>>
>>>>> http://www.w3.org/TR/2012/CR-html5-20121217/forms.html#attr-form-autocomplete
>>>>> for the input
>>>>>
>>>>> http://www.w3.org/TR/2012/CR-html5-20121217/forms.html#the-autocomplete-attribute
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Il giorno giovedì 18 luglio 2013 22:16:34 UTC+2, Jim S ha scritto:
>>>>>>
>>>>>> that may work for 1 browser but I can't require that all users of the
>>>>>> app turn off auto-complete.
>>>>>>
>>>>>>
>>>>>> On Thu, Jul 18, 2013 at 3:03 PM, Paolo Caruccio <
>>>>>> paolo.ca...@gmail.com> wrote:
>>>>>>
>>>>>>> How to Turn Off Form
>>>>>>> Autocompletion<https://developer.mozilla.org/en-US/docs/Mozilla/How_to_Turn_Off_Form_Autocompletion?redirectlocale=en-US&redirectslug=How_to_Turn_Off_Form_Autocompletion>
>>>>>>>
>>>>>>> Il giorno giovedì 18 luglio 2013 21:46:46 UTC+2, Jim S ha scritto:
>>>>>>>
>>>>>>>> I have no idea what version my calendar.js is. Is that something
>>>>>>>> that can just be overwritten whenever you do an update of web2py?
>>>>>>>>
>>>>>>>> Also, has this been addressed in more recent versions of web2py?
>>>>>>>>
>>>>>>>> -Jim
>>>>>>>>
>>>>>>>> On Thursday, July 18, 2013 2:30:58 PM UTC-5, Willoughby wrote:
>>>>>>>>>
>>>>>>>>> I believe you can override that (it's a browser feature) with
>>>>>>>>> HTML5:
>>>>>>>>> http://www.w3.org/wiki/HTML/**El**ements/input/text<http://www.w3.org/wiki/HTML/Elements/input/text>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Thursday, July 18, 2013 1:32:47 PM UTC-4, Jim S wrote:
>>>>>>>>>>
>>>>>>>>>> My main complaint with the current datetime picker is that you
>>>>>>>>>> can get in situations where (in Firefox at least) you can have a
>>>>>>>>>> dropdown
>>>>>>>>>> of previous entries appear over the calendar itself. See attached
>>>>>>>>>> screen
>>>>>>>>>> shot.
>>>>>>>>>>
>>>>>>>>>> -Jim
>>>>>>>>>>
>>>>>>>>>> On Wednesday, July 17, 2013 1:28:14 PM UTC-5, Annet wrote:
>>>>>>>>>>>
>>>>>>>>>>> I had a look at the datetime picker, I miss the month and year
>>>>>>>>>>> menus and the week of the year. Furthermore I find the
>>>>>>>>>>> display of dates in other months distracting, the styling could
>>>>>>>>>>> be a bit more calendar like.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Kind regards,
>>>>>>>>>>>
>>>>>>>>>>> Annet.
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>
>>>>>>> ---
>>>>>>> You received this message because you are subscribed to a topic in
>>>>>>> the Google Groups "web2py-users" group.
>>>>>>> To unsubscribe from this topic, visit https://groups.google.com/d/**
>>>>>>> topic/web2py/5NfsFtnv8Ww/**unsubscribe<https://groups.google.com/d/topic/web2py/5NfsFtnv8Ww/unsubscribe>
>>>>>>> .
>>>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>>>> web2py+un...@**googlegroups.com.
>>>>>>> For more options, visit
>>>>>>> https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out>
>>>>>>> .
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>
>>>>> ---
>>>>> You received this message because you are subscribed to a topic in the
>>>>> Google Groups "web2py-users" group.
>>>>> To unsubscribe from this topic, visit
>>>>> https://groups.google.com/d/topic/web2py/5NfsFtnv8Ww/unsubscribe.
>>>>> To unsubscribe from this group and all its topics, send an email to
>>>>> web2py+un...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>>>
>>>>>
>>>>>
>>>>
>>>>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
