commons-shared-web-ui 0.0.69 → 0.0.70
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/index.d.ts
CHANGED
|
@@ -1575,6 +1575,20 @@ declare class FormFieldComponent implements OnInit, AfterViewInit, OnDestroy {
|
|
|
1575
1575
|
onDateMonthSelected(date: Date, picker: {
|
|
1576
1576
|
close: () => void;
|
|
1577
1577
|
}): void;
|
|
1578
|
+
/**
|
|
1579
|
+
* Fired every time the picker opens (Material's (opened) output). `startView` only sets
|
|
1580
|
+
* the calendar's view on its very first render — clicking a year (in multi-year view)
|
|
1581
|
+
* also drives Material's OWN internal auto-drill (MatCalendar's `_goToDateInView`, called
|
|
1582
|
+
* as a side effect of the exact same click that fires (yearSelected)/(monthSelected)),
|
|
1583
|
+
* which advances the calendar's `currentView` to 'year' then 'month' regardless of our
|
|
1584
|
+
* close()-on-select handlers above. There's no public API to suppress that internal
|
|
1585
|
+
* drill, so for MONTH/YEAR granularity we defensively force the view back to
|
|
1586
|
+
* 'multi-year' on every open via Material's internal calendar reference — there's no
|
|
1587
|
+
* supported public way to do this, so it's wrapped in a try/catch and silently no-ops if
|
|
1588
|
+
* that internal shape ever changes in a future Material version. No-op entirely for
|
|
1589
|
+
* 'DAY' granularity, leaving default date fields completely untouched.
|
|
1590
|
+
*/
|
|
1591
|
+
onDatePickerOpened(picker: any): void;
|
|
1578
1592
|
isMultiDropdownOpen: boolean;
|
|
1579
1593
|
isSingleDropdownOpen: boolean;
|
|
1580
1594
|
dropdownCurrentPage: number;
|