-
Notifications
You must be signed in to change notification settings - Fork 12
[DO NOT MERGE] MaybeNativeDatePicker test branch #2892
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
Conversation
Addresses WB-2016
🦋 Changeset detectedLatest commit: 1ceea52 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Size Change: +6.03 kB (+5.53%) 🔍 Total Size: 115 kB
ℹ️ View Unchanged
|
A new build was pushed to Chromatic! 🚀https://5e1bf4b385e3fb0020b7073c-itrlwrlfpi.chromatic.com/ Chromatic results:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## feature/datepicker #2892 +/- ##
==========================================
==========================================
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
After testing on iOS and Android Emulators on the most common versions listed in https://caniuse.com/usage-table, I think we can safely drop the MaybeNativeDatePicker wrapper. The calendar overlay works fine on iOS Safari 18.6 and Chrome 134 (even older than the most common one, 142). |
Summary:
Test branch to determine whether we need
MaybeNativeDatePickeror justDatePicker. The frontend repo definitely uses this extra wrapper, but we removed it from the initial migration PR: #2876This draft PR exists to test this wrapper further and gather intel on it.
Issue: WB-1112
Test plan: