I've missed this in the review for #113, but the changes from #113 actually also changed the format output. For example:
new Intl.DurationFormat("en", {seconds: "numeric"}).format({seconds: 1, milliseconds: 3})
Returned "1.003" before #113, but is now returning "1".
It was returning "1.003", because when fractionalDigits = undefined was passed to the Intl.NumberFormat, the default minimum and maximum fractional digits from Intl.NumberFormat were applied. (mnfdDefault = 0 and mxfdDefault = 3 in InitializeNumberFormat.)
144 may resolve this issue anyway, but I still thought it's worthwhile to file an issue about it.
I've missed this in the review for #113, but the changes from #113 actually also changed the format output. For example:
Returned
"1.003"
before #113, but is now returning"1"
.It was returning
"1.003"
, because whenfractionalDigits = undefined
was passed to theIntl.NumberFormat
, the default minimum and maximum fractional digits fromIntl.NumberFormat
were applied. (mnfdDefault = 0
andmxfdDefault = 3
in InitializeNumberFormat.)144 may resolve this issue anyway, but I still thought it's worthwhile to file an issue about it.