I was led to believe that <input type="date"> doesn't work in thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> (bug 1527615) would be addressed in Thunderbird 68 before it was released to the public. Is that going to happen. There is functionality in Send Later that I can't provide in Thunderbird 68 unless <input type="date"> and <input type="time"> (replacing the removed <datepicker> and <timepicker> XUL elements) are working.   jik

Hey, unfortunately unclear if it will make it. What you can do if it doesn't, is to include datetimepickers.js <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> and use the datepicker and timepicker from lightning.  -Magnus On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: > > I was led to believe that <input type="date"> doesn't work in > thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> > (bug 1527615) would be addressed in Thunderbird 68 before it was > released to the public. Is that going to happen. There is > functionality in Send Later that I can't provide in Thunderbird 68 > unless <input type="date"> and <input type="time"> (replacing the > removed <datepicker> and <timepicker> XUL elements) are working. > >   jik > > > > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

On 6/6/19 3:28 PM, Magnus Melin wrote: > > Hey, unfortunately unclear if it will make it. What you can do if it > doesn't, is to include datetimepickers.js > <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> > and use the datepicker and timepicker from lightning. > >  -Magnus > > On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: >> >> I was led to believe that <input type="date"> doesn't work in >> thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> >> (bug 1527615) would be addressed in Thunderbird 68 before it was >> released to the public. Is that going to happen. There is >> functionality in Send Later that I can't provide in Thunderbird 68 >> unless <input type="date"> and <input type="time"> (replacing the >> removed <datepicker> and <timepicker> XUL elements) are working. >> >>   jik >> >> >> >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Thanks, taking care of that in https://bugzilla.mozilla.org/show_bug.cgi?id=1557624  -Magnus On 07-06-2019 00:25, Jonathan Kamens wrote: > > On 6/6/19 3:28 PM, Magnus Melin wrote: >> >> Hey, unfortunately unclear if it will make it. What you can do if it >> doesn't, is to include datetimepickers.js >> <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> >> and use the datepicker and timepicker from lightning. >> >>  -Magnus >> >> On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: >>> >>> I was led to believe that <input type="date"> doesn't work in >>> thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> >>> (bug 1527615) would be addressed in Thunderbird 68 before it was >>> released to the public. Is that going to happen. There is >>> functionality in Send Later that I can't provide in Thunderbird 68 >>> unless <input type="date"> and <input type="time"> (replacing the >>> removed <datepicker> and <timepicker> XUL elements) are working. >>> >>>   jik >>> >>> >>> >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Even now that that bug is resolved I am still unable to use <datepicker> or <timepicker> from Lightning in my add-on. I've attached a very simple XUL file which attempts to instantiate these objects. Below is what I see in the console when I attempt to instantiate this XUL file with window.openDialog. Am I doing something wrong? Also, even if we get all these kinks worked out and get this resolved, are my users going to have to have the Lightning add-on enabled in order for <datepicker> and <timepicker> from Lightning to work in my add-on? Because if so, that's a non-starter, I can't demand that my users enable Lightning, which adds all sorts of UI elements that many of them aren't going to want.   jik TypeError: "this._inputField is undefined" customElements.js:196:28 set _inputBoxValuechrome://calendar/content/datetimepickers/datetimepickers.js:887 set valuechrome://calendar/content/datetimepickers/datetimepickers.js:864 connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:768 <anonymous>chrome://global/content/customElements.js:194 <anonymous>debugger eval code:1 getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 evaluateJSresource://devtools/server/actors/webconsole.js:1008 evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 onPacketresource://devtools/server/main.js:1291 sendresource://devtools/shared/transport/local-transport.js:64 makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 TypeError: "this._popup is undefined" customElements.js:196:28 connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:922 <anonymous>chrome://global/content/customElements.js:194 <anonymous>debugger eval code:1 getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 evaluateJSresource://devtools/server/actors/webconsole.js:1008 evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 onPacketresource://devtools/server/main.js:1291 sendresource://devtools/shared/transport/local-transport.js:64 makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 <anonymous>chrome://global/content/customElements.js:196 <anonymous>debugger eval code:1 getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 evaluateJSresource://devtools/server/actors/webconsole.js:1008 evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 onPacketresource://devtools/server/main.js:1291 sendresource://devtools/shared/transport/local-transport.js:64 makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 ChromeWindow > Thanks, taking care of that in > https://bugzilla.mozilla.org/show_bug.cgi?id=1557624 > >  -Magnus > > On 07-06-2019 00:25, Jonathan Kamens wrote: >> >> On 6/6/19 3:28 PM, Magnus Melin wrote: >>> >>> Hey, unfortunately unclear if it will make it. What you can do if it >>> doesn't, is to include datetimepickers.js >>> <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> >>> and use the datepicker and timepicker from lightning. >>> >>>  -Magnus >>> >>> On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: >>>> >>>> I was led to believe that <input type="date"> doesn't work in >>>> thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> >>>> (bug 1527615) would be addressed in Thunderbird 68 before it was >>>> released to the public. Is that going to happen. There is >>>> functionality in Send Later that I can't provide in Thunderbird 68 >>>> unless <input type="date"> and <input type="time"> (replacing the >>>> removed <datepicker> and <timepicker> XUL elements) are working. >>>> >>>>   jik >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

You could include the datetimepickers code with your extension. It's at calendar/resources/content/datetimepickers/datetimepickers.js. GL On 12/06/19 07:21, Jonathan Kamens via Maildev wrote: > > Even now that that bug is resolved I am still unable to use > <datepicker> or <timepicker> from Lightning in my add-on. > > I've attached a very simple XUL file which attempts to instantiate > these objects. > > Below is what I see in the console when I attempt to instantiate this > XUL file with window.openDialog. > > Am I doing something wrong? > > Also, even if we get all these kinks worked out and get this resolved, > are my users going to have to have the Lightning add-on enabled in > order for <datepicker> and <timepicker> from Lightning to work in my > add-on? Because if so, that's a non-starter, I can't demand that my > users enable Lightning, which adds all sorts of UI elements that many > of them aren't going to want. > >   jik > > TypeError: "this._inputField is undefined" customElements.js:196:28 > set > _inputBoxValuechrome://calendar/content/datetimepickers/datetimepickers.js:887 > set valuechrome://calendar/content/datetimepickers/datetimepickers.js:864 > connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:768 > <anonymous>chrome://global/content/customElements.js:194 > <anonymous>debugger eval code:1 > getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 > evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 > evaluateJSresource://devtools/server/actors/webconsole.js:1008 > evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 > onPacketresource://devtools/server/main.js:1291 > sendresource://devtools/shared/transport/local-transport.js:64 > makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 > makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 > TypeError: "this._popup is undefined" customElements.js:196:28 > connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:922 > <anonymous>chrome://global/content/customElements.js:194 > <anonymous>debugger eval code:1 > getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 > evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 > evaluateJSresource://devtools/server/actors/webconsole.js:1008 > evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 > onPacketresource://devtools/server/main.js:1291 > sendresource://devtools/shared/transport/local-transport.js:64 > makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 > makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 > <anonymous>chrome://global/content/customElements.js:196 > <anonymous>debugger eval code:1 > getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 > evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 > evaluateJSresource://devtools/server/actors/webconsole.js:1008 > evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 > onPacketresource://devtools/server/main.js:1291 > sendresource://devtools/shared/transport/local-transport.js:64 > makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 > makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 > ChromeWindow > >> Thanks, taking care of that in >> https://bugzilla.mozilla.org/show_bug.cgi?id=1557624 >> >>  -Magnus >> >> On 07-06-2019 00:25, Jonathan Kamens wrote: >>> >>> On 6/6/19 3:28 PM, Magnus Melin wrote: >>>> >>>> Hey, unfortunately unclear if it will make it. What you can do if >>>> it doesn't, is to include datetimepickers.js >>>> <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> >>>> and use the datepicker and timepicker from lightning. >>>> >>>>  -Magnus >>>> >>>> On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: >>>>> >>>>> I was led to believe that <input type="date"> doesn't work in >>>>> thunderbird <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> >>>>> (bug 1527615) would be addressed in Thunderbird 68 before it was >>>>> released to the public. Is that going to happen. There is >>>>> functionality in Send Later that I can't provide in Thunderbird 68 >>>>> unless <input type="date"> and <input type="time"> (replacing the >>>>> removed <datepicker> and <timepicker> XUL elements) are working. >>>>> >>>>>   jik >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Maildev mailing list >>>>> Maildev@lists.thunderbird.net >>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>> >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

I played around with the datetimepicker, can someone confirm my findings? 1. You must include the following CSS files: <?xml-stylesheet type="text/css" href="chrome://calendar-common/skin/widgets/minimonth.css"?> <?xml-stylesheet type="text/css" href="chrome://calendar/content/widgets/calendar-widget-bindings.css"?> <?xml-stylesheet type="text/css" href="chrome://lightning-common/skin/datetimepickers.css"?> 2. You must include the following JS files:   <script src="chrome://calendar/content/calendar-ui-utils.js"/>   <script src="chrome://messenger/content/customElements.js"/>   <script src="chrome://calendar/content/datetimepickers/datetimepickers.js"/> 3. To insert the datetimepicker, just do       <datetimepicker id="myDateTimePicker" /> 4. The value is a javascript Date object, so this works       document.getElementById("myDateTimePicker").value = new Date('December 17, 1995 03:24:00'); I was not able to get it to work with less files included, but there could be some other trick. Do I need all of these files? I will add that info to the guide, if no one has other information. John Am 12.06.2019 um 00:47 schrieb Geoff Lankow: > > You could include the datetimepickers code with your extension. It's > at calendar/resources/content/datetimepickers/datetimepickers.js. > > GL > > On 12/06/19 07:21, Jonathan Kamens via Maildev wrote: >> >> Even now that that bug is resolved I am still unable to use >> <datepicker> or <timepicker> from Lightning in my add-on. >> >> I've attached a very simple XUL file which attempts to instantiate >> these objects. >> >> Below is what I see in the console when I attempt to instantiate this >> XUL file with window.openDialog. >> >> Am I doing something wrong? >> >> Also, even if we get all these kinks worked out and get this >> resolved, are my users going to have to have the Lightning add-on >> enabled in order for <datepicker> and <timepicker> from Lightning to >> work in my add-on? Because if so, that's a non-starter, I can't >> demand that my users enable Lightning, which adds all sorts of UI >> elements that many of them aren't going to want. >> >>   jik >> >> TypeError: "this._inputField is undefined" customElements.js:196:28 >> set >> _inputBoxValuechrome://calendar/content/datetimepickers/datetimepickers.js:887 >> set valuechrome://calendar/content/datetimepickers/datetimepickers.js:864 >> connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:768 >> <anonymous>chrome://global/content/customElements.js:194 >> <anonymous>debugger eval code:1 >> getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 >> evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 >> evaluateJSresource://devtools/server/actors/webconsole.js:1008 >> evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 >> onPacketresource://devtools/server/main.js:1291 >> sendresource://devtools/shared/transport/local-transport.js:64 >> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >> TypeError: "this._popup is undefined" customElements.js:196:28 >> connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:922 >> <anonymous>chrome://global/content/customElements.js:194 >> <anonymous>debugger eval code:1 >> getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 >> evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 >> evaluateJSresource://devtools/server/actors/webconsole.js:1008 >> evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 >> onPacketresource://devtools/server/main.js:1291 >> sendresource://devtools/shared/transport/local-transport.js:64 >> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >> <anonymous>chrome://global/content/customElements.js:196 >> <anonymous>debugger eval code:1 >> getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 >> evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 >> evaluateJSresource://devtools/server/actors/webconsole.js:1008 >> evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 >> onPacketresource://devtools/server/main.js:1291 >> sendresource://devtools/shared/transport/local-transport.js:64 >> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >> ChromeWindow >> >>> Thanks, taking care of that in >>> https://bugzilla.mozilla.org/show_bug.cgi?id=1557624 >>> >>>  -Magnus >>> >>> On 07-06-2019 00:25, Jonathan Kamens wrote: >>>> >>>> On 6/6/19 3:28 PM, Magnus Melin wrote: >>>>> >>>>> Hey, unfortunately unclear if it will make it. What you can do if >>>>> it doesn't, is to include datetimepickers.js >>>>> <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> >>>>> and use the datepicker and timepicker from lightning. >>>>> >>>>>  -Magnus >>>>> >>>>> On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: >>>>>> >>>>>> I was led to believe that <input type="date"> doesn't work in >>>>>> thunderbird >>>>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> (bug >>>>>> 1527615) would be addressed in Thunderbird 68 before it was >>>>>> released to the public. Is that going to happen. There is >>>>>> functionality in Send Later that I can't provide in Thunderbird >>>>>> 68 unless <input type="date"> and <input type="time"> (replacing >>>>>> the removed <datepicker> and <timepicker> XUL elements) are working. >>>>>> >>>>>>   jik >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Maildev mailing list >>>>>> Maildev@lists.thunderbird.net >>>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>>> >>>>> _______________________________________________ >>>>> Maildev mailing list >>>>> Maildev@lists.thunderbird.net >>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net

Thanks very much, yes, that seems to be sufficient to me. See the branch in which I tested this successfully at https://github.com/jikamens/send-later/tree/lightning_date_time_pickers. I did notice one error in the error console when instantiating a window with a Lightning datepicker and timepicker in it, but apparently it's harmless. However, as noted previously, it only works when Lightning is enabled. I can't require the users of my add-on to enable Lightning, and I don't think it would be reasonable for any other add-on maintainers to require that just for the sake of using Lightning's datepicker or timepicker, unless their add-on enhances Lightning specifically so it wouldn't make sense to have it without Lightning. And while I appreciate Geoff's suggestion, I am rather and I think understandably reluctant to copy the code from at least six different CSS and JavaScript files from Lightning to my add-on to acquire this functionality. It's probably actually more than six, since two of the six are skin files which means there are probably different versions for different skins and any of the six files might include others.   jik On 6/13/19 3:06 PM, John Bieling wrote: > > I played around with the datetimepicker, can someone confirm my findings? > > 1. You must include the following CSS files: > > <?xml-stylesheet type="text/css" > href="chrome://calendar-common/skin/widgets/minimonth.css"?> > <?xml-stylesheet type="text/css" > href="chrome://calendar/content/widgets/calendar-widget-bindings.css"?> > <?xml-stylesheet type="text/css" > href="chrome://lightning-common/skin/datetimepickers.css"?> > > 2. You must include the following JS files: > >   <script src="chrome://calendar/content/calendar-ui-utils.js"/> >   <script src="chrome://messenger/content/customElements.js"/> >   <script > src="chrome://calendar/content/datetimepickers/datetimepickers.js"/> > > 3. To insert the datetimepicker, just do > >       <datetimepicker id="myDateTimePicker" /> > > 4. The value is a javascript Date object, so this works > >       document.getElementById("myDateTimePicker").value = new > Date('December 17, 1995 03:24:00'); > > I was not able to get it to work with less files included, but there > could be some other trick. Do I need all of these files? > > I will add that info to the guide, if no one has other information. > > John > > > > > Am 12.06.2019 um 00:47 schrieb Geoff Lankow: >> >> You could include the datetimepickers code with your extension. It's >> at calendar/resources/content/datetimepickers/datetimepickers.js. >> >> GL >> >> On 12/06/19 07:21, Jonathan Kamens via Maildev wrote: >>> >>> Even now that that bug is resolved I am still unable to use >>> <datepicker> or <timepicker> from Lightning in my add-on. >>> >>> I've attached a very simple XUL file which attempts to instantiate >>> these objects. >>> >>> Below is what I see in the console when I attempt to instantiate >>> this XUL file with window.openDialog. >>> >>> Am I doing something wrong? >>> >>> Also, even if we get all these kinks worked out and get this >>> resolved, are my users going to have to have the Lightning add-on >>> enabled in order for <datepicker> and <timepicker> from Lightning to >>> work in my add-on? Because if so, that's a non-starter, I can't >>> demand that my users enable Lightning, which adds all sorts of UI >>> elements that many of them aren't going to want. >>> >>>   jik >>> >>> TypeError: "this._inputField is undefined" customElements.js:196:28 >>> set >>> _inputBoxValuechrome://calendar/content/datetimepickers/datetimepickers.js:887 >>> set >>> valuechrome://calendar/content/datetimepickers/datetimepickers.js:864 >>> connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:768 >>> <anonymous>chrome://global/content/customElements.js:194 >>> <anonymous>debugger eval code:1 >>> getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 >>> evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 >>> evaluateJSresource://devtools/server/actors/webconsole.js:1008 >>> evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 >>> onPacketresource://devtools/server/main.js:1291 >>> sendresource://devtools/shared/transport/local-transport.js:64 >>> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >>> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >>> TypeError: "this._popup is undefined" customElements.js:196:28 >>> connectedCallbackchrome://calendar/content/datetimepickers/datetimepickers.js:922 >>> <anonymous>chrome://global/content/customElements.js:194 >>> <anonymous>debugger eval code:1 >>> getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 >>> evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 >>> evaluateJSresource://devtools/server/actors/webconsole.js:1008 >>> evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 >>> onPacketresource://devtools/server/main.js:1291 >>> sendresource://devtools/shared/transport/local-transport.js:64 >>> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >>> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >>> <anonymous>chrome://global/content/customElements.js:196 >>> <anonymous>debugger eval code:1 >>> getEvalResultresource://devtools/server/actors/webconsole/eval-with-debugger.js:134 >>> evalWithDebuggerresource://devtools/server/actors/webconsole/eval-with-debugger.js:105 >>> evaluateJSresource://devtools/server/actors/webconsole.js:1008 >>> evaluateJSAsyncresource://devtools/server/actors/webconsole.js:912 >>> onPacketresource://devtools/server/main.js:1291 >>> sendresource://devtools/shared/transport/local-transport.js:64 >>> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >>> makeInfallibleresource://devtools/shared/ThreadSafeDevToolsUtils.js:109 >>> ChromeWindow >>> >>>> Thanks, taking care of that in >>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1557624 >>>> >>>>  -Magnus >>>> >>>> On 07-06-2019 00:25, Jonathan Kamens wrote: >>>>> >>>>> On 6/6/19 3:28 PM, Magnus Melin wrote: >>>>>> >>>>>> Hey, unfortunately unclear if it will make it. What you can do if >>>>>> it doesn't, is to include datetimepickers.js >>>>>> <https://searchfox.org/comm-central/source/calendar/resources/content/datetimepickers/datetimepickers.js> >>>>>> and use the datepicker and timepicker from lightning. >>>>>> >>>>>>  -Magnus >>>>>> >>>>>> On 06-06-2019 14:51, Jonathan Kamens via Maildev wrote: >>>>>>> >>>>>>> I was led to believe that <input type="date"> doesn't work in >>>>>>> thunderbird >>>>>>> <https://bugzilla.mozilla.org/show_bug.cgi?id=1527615> (bug >>>>>>> 1527615) would be addressed in Thunderbird 68 before it was >>>>>>> released to the public. Is that going to happen. There is >>>>>>> functionality in Send Later that I can't provide in Thunderbird >>>>>>> 68 unless <input type="date"> and <input type="time"> (replacing >>>>>>> the removed <datepicker> and <timepicker> XUL elements) are working. >>>>>>> >>>>>>>   jik >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Maildev mailing list >>>>>>> Maildev@lists.thunderbird.net >>>>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>>>> >>>>>> _______________________________________________ >>>>>> Maildev mailing list >>>>>> Maildev@lists.thunderbird.net >>>>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>>> >>>> _______________________________________________ >>>> Maildev mailing list >>>> Maildev@lists.thunderbird.net >>>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >>> >>> _______________________________________________ >>> Maildev mailing list >>> Maildev@lists.thunderbird.net >>> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net >> >> _______________________________________________ >> Maildev mailing list >> Maildev@lists.thunderbird.net >> http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net > > _______________________________________________ > Maildev mailing list > Maildev@lists.thunderbird.net > http://lists.thunderbird.net/mailman/listinfo/maildev_lists.thunderbird.net