bug: datetime, month/year selection with cancel/done buttons has confusing UX

Prerequisites

• I have read the Contributing Guidelines.
• I agree to follow the Code of Conduct.
• I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request

Event should be emitted when user changes view from default to month/year selection opened when clicked on top left button in the datepicker and back to default view.

Describe the Use Case

I am showing ion-datetime in a modal. When I want to select a date in one of the past years, I must click on the month/date button in top left corner. If I then select wanted month and year, and click on done, modal closes and value is set to previously select date. This behaviour is frustrating, because many users don’t expect modal to be closed with previously selected value.

Describe Preferred Solution

If an event is emitted when these views are toggled, we can handle custom behaviour (show and hide DONE button for example) and prevent users from exiting modal unintentionally.

Describe Alternatives

No response

Related Code

<ion-button id="open-modal">Open Datetime Modal</ion-button>
<ion-modal trigger="open-modal" [backdropDismiss]="false">
  <ng-template>
    <ion-content>
      <ion-datetime
        size="cover"
        [disabled]="false"
        [max]="'2050-12-31'"
        [(ngModel)]="date"
        (ionChange)="updateValue($event)"
        [showDefaultButtons]="true"
      >
      </ion-datetime>
    </ion-content>
  </ng-template>
</ion-modal>

Additional Information

https://user-images.githubusercontent.com/85163599/160097525-deb50edf-1c29-4f08-9c72-6fe5d7cc979a.mov

[babycourageous]

@realappie if it is any help I have used a variation on this suggestion while the ionic team works on tackling this bug - https://github.com/ionic-team/ionic-framework/issues/24962#issuecomment-1093108511

[ionitron-bot[bot]]

Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.