Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: ensure focused month is visible when receiving focus (#3219) (CP: 22.0) #3273

Merged
merged 1 commit into from
Jan 10, 2022

Conversation

vursen
Copy link
Contributor

@vursen vursen commented Jan 7, 2022

Description

A cherry-pick of #3219 to version 22.0.

Fixes #1892.

Type of change

  • Bugfix

Checklist

  • I have read the contribution guide: https://vaadin.com/docs-beta/latest/guide/contributing/overview/
  • I have added a description following the guideline.
  • The issue is created in the corresponding repository and I have referenced it.
  • I have added tests to ensure my change is effective and works as intended.
  • New and existing tests are passing locally with my change.
  • I have performed self-review and corrected misspellings.

@vursen vursen changed the base branch from master to 22.0 January 7, 2022 13:44
@web-padawan web-padawan force-pushed the cp/ensure-focused-month-is-visible branch from 931b4a1 to c4f9980 Compare January 10, 2022 09:26
@sonarcloud
Copy link

sonarcloud bot commented Jan 10, 2022

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@web-padawan web-padawan merged commit 9bfa882 into 22.0 Jan 10, 2022
@web-padawan web-padawan deleted the cp/ensure-focused-month-is-visible branch January 10, 2022 09:41
@vaadin-bot
Copy link
Collaborator

This ticket/PR has been released with platform 22.0.3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants