On 25/12/2018 17:43, opto wrote:
> Previously dateValue did preset the Date when given a js date(), see MDN. No longer. Is there a workaround? How does lightning do it?
> I am already using the new bindings.
We forked date picker to c-c. I'm not aware of any (intentional)
changes. Lightning does its own thing, only consumer I know is the "Send
Later" add-on by Jonathan Kamens. I suggest to check its code.
After an evening of reading (I am now in another timezone) and finding that bug already, I just now noticed that the new (?) definition of datepicker is in disagreement to MDN and to previous use of datepicker in the addon I am updating.
MDN: value has a string value of date: YYYY-MM-DD, dateValue has the js Date.
Actual behaviour: value is Date.
Lightning is identical to current behaviour.
So the workaround is to replace dateValue with value.
I will put a note into MDN, the addons 57 document and open a bug so it can be decided which behaviour is wanted.
yes - sorry for the confusion. I will reverse the documents.
Amazing that that addon worked with dateValue before TB 45 and does not now - that is the reason for all that hassle. Why does it link into calendar now and did not do before? Or maybe they changed their definition and were identical to base TB before?