-
Notifications
You must be signed in to change notification settings - Fork 53
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(ia): refresh on audience setup complete #3839
base: trunk
Are you sure you want to change the base?
Conversation
…3495) * feat(ia-admin-header-selected): Allow ability to force selected tab * Update src/wizards/admin-header/index.tsx Co-authored-by: Jared Rethman <[email protected]> --------- Co-authored-by: Jared Rethman <[email protected]>
…brands feat(ia): settings additional brands
…ging fix: only apply merging to plain objects
Co-authored-by: Miguel Peixe <[email protected]>
Co-authored-by: Miguel Peixe <[email protected]>
feat(ras): allow skipping prerequisites; avoid dead end in onboarding
fix(recaptcha): remove v3 from heading; preserve settings on toggle
This PR adds the suppression tab back into the Advertising wizard
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.
This fixes the issue, but now this introduces some strangeness in the UI. After completing setup, the page appears to reload twice as a result of calling replace and then reload:
Screen.Recording.2025-03-18.at.12.34.39.mov
Maybe we can replace both of these with window.location.href = url
?
That will have the same behavior as How about 7318b60? |
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.
How about 7318b60?
Thanks for clarifying! I am still seeing this strange double reload in the UI with this change:
Screen.Recording.2025-03-19.at.14.56.06.mov
It would be great if we could remain in the completed card until the reload triggers.
Hmm, that's strange. I can't reproduce it. Which browser is that? |
This is on Firefox 136.0.2 |
All Submissions:
Changes proposed in this Pull Request:
1205919985867982-as-1209464932054174/f
After the audience setup, a full page refresh is required. The current approach runs only a
window.location.replace()
which will not do a full page load if the replacement is just a hash change.This PR forces a reload after the location is replaced.
How to test the changes in this Pull Request:
Other information: