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
CYS - Core: install font when user clicks opt-in #45580
CYS - Core: install font when user clicks opt-in #45580
Conversation
Test Results SummaryCommit SHA: cdb7799
To view the full API test report, click here. To view the full E2E test report, click here. To view all test reports, visit the WooCommerce Test Reports Dashboard. |
71d8240
to
4439716
Compare
…er-clicking-start-designing-1' of github.com:woocommerce/woocommerce into 45476-cys-on-core-make-sure-the-pre-loader-is-triggered-right-after-the-user-clicks-on-the-opt-in-modal
Hi @albarin, @nefeline, @woocommerce/woo-fse Apart from reviewing the code changes, please make sure to review the testing instructions as well. You can follow this guide to find out what good testing instructions should look like: |
…er-clicking-start-designing-1' of github.com:woocommerce/woocommerce into 45476-cys-on-core-make-sure-the-pre-loader-is-triggered-right-after-the-user-clicks-on-the-opt-in-modal
…-cys-on-core-make-sure-the-pre-loader-is-triggered-right-after-the-user-clicks-on-the-opt-in-modal
…-cys-on-core-make-sure-the-pre-loader-is-triggered-right-after-the-user-clicks-on-the-opt-in-modal
…-cys-on-core-make-sure-the-pre-loader-is-triggered-right-after-the-user-clicks-on-the-opt-in-modal
e7cdfba
to
06c19fa
Compare
@albarin, @nefeline and @verofasulo. This PR introduces this UX: Please note that after installation, clicking on "Choose Fonts" will not select any font pair. This is because the theme continues to use the previously chosen font by default: Should we consider updating the theme to utilize the newly installed font (Inter -Inter) during the installation process? |
@@ -201,18 +202,16 @@ export const SidebarNavigationScreenTypography = () => { | |||
</Button> | |||
<Button | |||
onClick={ async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the async
still needed here or can this be a regular arrow fn now that we removed the await
portion below?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch! Fixed!
Nit: I'm not sure if it's appropriate to address in this PR but it seems like the Having |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ensure that the pre-load screen appears
I've tried to run the testing steps 4 times and each time it freezes at the Turning on the lights step.
I can move forward in the process by refreshing the page but if I don't refresh, it will just hang.
CleanShot.2024-03-15.at.21.59.45.mp4
@danielwrobert could you please direct any questions related to design and/or copy to @verofasulo and @lauroraa ? Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your work here, @gigitux! I've requested a change in the code: let's keep both async and sync fonts installation in place in case one of them happen to fail 👍
Regarding:
and each time it freezes at the Turning on the lights step.
I can reproduce this as well: unfortunately, the console has no particular errors that could help with debugging.
...-admin/client/customize-store/assembler-hub/sidebar/sidebar-navigation-screen-typography.tsx
Show resolved
Hide resolved
I can reproduce this as well. |
Sorry for the confusion, I introduced the issue with 00eb4a3. I fixed it! Also, I noticed that the font installation wasn't triggered when the assembler wasn't loaded in the iframe. I fixed that issue as well! 🤞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great effort 🙇
Tests as expected now!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the amazing work! Confirmed things are working as expected now 🚀
Warning
This PR is blocked by #45586
Submission Review Guidelines:
Changes proposed in this Pull Request:
Closes #45476 .
How to test the changes in this Pull Request:
Using the WooCommerce Testing Instructions Guide, include your detailed testing instructions:
customize-store
is enabledReset Customize Your Store
-wp-admin/admin.php?page=wc-settings&tab=advanced§ion=woocommerce_com
Allow usage of WooCommerce to be tracked
is disabled.wp-admin/admin.php?page=wc-admin&path=%2Fcustomize-store
.Start designing
.Change homepage
.Choose Fonts
.Opt in to usage tracking to get access to more fonts
.usage tracking
.SELECT * FROM
wp_posts
WHEREpost_type
LIKE 'wp_font_face'DELETE FROM
wp_posts
WHEREpost_type
= 'wp_font_face';DELETE FROM
wp_posts
WHEREpost_type
= 'wp_font_family';