Describe the bug
In IE, when the dayjs object is generated by Date object, the formatted string of milli seconds show '000' always.
Please see this JSFiddle.
(https://jsfiddle.net/7jrdo1bz/)

It seems be correct behavior when dayjs object is generated by unix milliseconds.
(like: dayjs(1575441029123))

Expected behavior
Show correct milli seconds.

Information

• Day.js Ver

parseISO v2 documentation currently states

The previous parse implementation was renamed to parseISO.

parse v2 documentation currently states

Old parse was renamed to toDate. Now parse is a new function which parses a string using a provided format.

I think considering the sentence is to divert people who have previously been using v1 parse to the correct v2 equivalent, it only

I'd like to contribute to the documentation by adding some of the available options which are not currently documented on the site.

An example of that is the minuteIncrement config that I had dive into the documentation to find it myself. I'm sure a few people might have had a need for this but never found it.

Which repo do I need to fork to be able to contribute this to the documentation?

Thank you for your work on pickadate!

As far as I can tell, pickadate works nicely with jQuery's slim build; if that is in fact the case (and long-term intent), it might be worth mentioning that.

Feature Request

Pendulum has a nice feature that allows you to make a function call on a Pendulum object to automatically get a pre-formatted, c

The docs on
https://github.com/malcommac/SwiftDate/wiki/1.-Introduction:-Absolute-Date-and-DateInRegion
says

let dateFormat = "yyyy-MM-dd HH:mm"
let current_default = Date.defaultRegion
// Print date in current local device region
print(now.string(format: .custom(dateFormat))) // 2017-04-09 19:32
// Change the default region
Date.setDefaultRegion(regionNY)
// Print it again; now the

Parsing token 'x' according to documentation it should parse to microseconds timestamp but it parses to milliseconds timestamp. Not sure what was intended here but there is a discrepancy.
code:
_TOKENS = ( ... "x": lambda dt: "{:d}".format(dt.int_timestamp * 1000 + dt.microsecond // 1000)

'onclick' events are broken under iOS 13 wkwebview. More details here: facebook/react#17258

The solution is to use 'onTap' detection, which works with both click and all touch devices.

Good libraries for that :
https://github.com/GianlucaGuarini/Tocca.js
https://github.com/hammerjs/hammer.js/

the first screenshot is the dates being handled by iOS 11. The second screenshot is the dates being handles by iOS 10.

First, there is a row where the exact timestamps pulled from parse are printed, then a row showing what happens to the timestamps after .endOfDay is called and then I try to calculate the number of days between the two dates.

`

     if let start = se

The documentation mentions that an "opened" event will be fired when the calendar is opened, but this is not true, no such event exists.

I'd like an /Examples folder with some simple iOS apps showing how to use Time.

The first one that comes to mind is a basic iOS app using a UICollectionView to build a month calendar view.

USE_AUTOLOAD=0 is set if USE_SYSTEM_TZ_DB is true and USE_AUTOLOAD=1 otherwise. What is it for? I can't see anything that it is attached to. Is it to do with CURL?

Perhaps some documentation (in README or inline comments) on this and HAS_REMOTE_API would be useful?

I added the CalendarView in a ConstraintLayout which I set as the view in a DialogFragment. When the dialog is shown, you see the calendar but then the calendar flashes. Additionally if you scroll to the next month, that month also flashes. After the initial flash upon loading, it is not seen again (until a new instance of the dialog is created).

The CalendarView has its width and height set to

It would be nice if we could pretty print a range. For instance :

"on April 1st between 10:45 and 11:45"
"between April 1st and April 3rd"
"between April 1st at 9:00 and April 3rd at 18:00"
"on April 1st at 10:45 for 1 hour"

Not sure what the API would be though.

In relation with #308 it's unclear what value should be passed to value prop when using selectRange={true}.
For now, I set value once as date object (when user select first date), then I set as an array of 2 date objects (when user select range). When clearing selection I set null.

Is it a good approach to change the type of the variable used as a value in Calendar component?

While there are some issues/PRs (#243, #284, etc.) relating to wasm, there is no specific section in documentation properly detailing steps to use it with something like wasm-pack.

For now (v0.4.10), the following code fails to compile:

extern crate wasm_bindgen;

use wasm_bindgen::prelude::*;
use chrono::{NaiveDate};

#[wasm_bindgen]
pub struct Request {
    date: NaiveDat

Many people coming to this library were previously using MomentJS and Luxon. And in those libraries, it's very common to utilize moment().startOf("day"). I think it would be great to have some kind of documentation to help those coming from MomentJS or Luxon to quickly be able to utilize the correct API method.

I've done my best to document what I believe the options are in [this StackOverflo