-
Notifications
You must be signed in to change notification settings - Fork 72
Remove fraud protection discoverability and update tour #10558
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
Remove fraud protection discoverability and update tour #10558
Conversation
Test the buildOption 1. Jetpack Beta
Option 2. Jurassic Ninja - available for logged-in A12s🚀 Launch a JN site with this branch 🚀 ℹ️ Install this Tampermonkey script to get more options. Build info:
Note: the build is updated when a new commit is pushed to this PR. |
|
Size Change: -34 kB (-3%) Total Size: 1.27 MB
ℹ️ View Unchanged
|
|
@ismaeldcom Is there any way to add some sort of padding at the top on mobile? When I test in that view, the automatic scrolling scrolls the highlighted section to the top, but that gets hidden behind the header bar. |
Great catch @jessepearson, I somehow misplaced Let me know what you think after pulling 28994a4 🙂 |
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.
# Conflicts: # client/overview/index.js
|
👋 @ismaeldcom - It seems there are still some leftovers, which makes me a bit confused when looking at the relevant option keys. I remembered that last week, I could see the banner but with the latest
woocommerce-payments/client/globals.d.ts Line 117 in fff213c
|











Fixes #9726
Changes proposed in this Pull Request
fraud-risk-tools-bannercode.new featurewording.The issue criteria is
show for new merchants the first time they navigate to the Payments → Settings page, but after testing I think it leads to an awkward user experience as they are presented with it directly. Instead, I've decided to show it when the fraud settings are visible, either by scrolling or directly linking.Since the boxes were all over the place, I updated their referenced elements and switched to spotlight mode, which points to a specific part better. And fixed the arrow and mobile issues.
Testing instructions
npm run build:clientScreenshots
npm run changelogto add a changelog file, choosepatchto leave it empty if the change is not significant. You can add multiple changelog files in one PR by running this command a few times.Post merge