coreui / coreui-pro / 36870577390

96%

main: 94%

push

github

fix(Calendar): keep the day a series of page turns started from (#1511)

* fix(Calendar): keep the day a series of page turns started from

Page Down and Page Up cut the day to the length of the target month and
then carried the cut day on, so January 31 went to February 28 and then to
March 28. The page action now returns the day it kept, the calendar passes
it back while the focus is still on the date the last turn reached, and
January 31 goes to February 28 and then to March 31. Any other key starts
a new series.

* fix(Calendar): keep the page-turn day through limits and week rows

A turn that minDate or maxDate blocked dropped the kept day, week rows never
matched it because the next key reports the first day of the row, and a
click left it in place. The util now returns the kept day ready to pass back,
dated on the first day of the row for week rows, a blocked turn keeps it, and
a click clears it.

* fix(Calendar): end a page-turn series on any other key and turn week rows from their month

A week row that starts in the previous month turned from that month, so the
second turn of a series aimed at the row it was already on and paged the
calendar past maxDate. The kept day now also carries the date the turn aimed
at, and the next turn starts from its month. getKeptDay decides what a key
leaves behind: the day a turn returns, the held day while a turn is blocked
or only a modifier is pressed, nothing after any other key, the grid's own
keys included; a click anywhere in the calendar clears it. The date picker's
keyboard table and the Shift rows say the same.

* chore: raise the JS bundle budgets for the page-turn series

Measured against v6-dev with gzip -9 on the built bundles: coreui.bundle.js
+629 B, coreui.esm.js +634 B, coreui.js +631 B (most of it the util's JSDoc,
which the unminified bundles keep), coreui.min.js +164 B. The three
unminified bundles went over their ceilings and coreui.min.js was left with
30 B, so each ceiling now keeps at ... (continued)

6663 of 7211 branches covered (92.4%)

Branch coverage included in aggregate %.

19 of 19 new or added lines in 2 files covered. (100.0%)

11784 of 12078 relevant lines covered (97.57%)

1382.2 hits per line