Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
In the expense-view Supplier flow I inspected,
MoneyRequestViewalready passesgetReportRHPActiveRoute()intoROUTES.MONEY_REQUEST_STEP_VENDOR.getRoute(...), and the tab-swap code inlinkTo/swapBackgroundTabForRHPTargetonly checks the runtimeroute.params.backTo. This newbackToentry is just a TypeScript param-list annotation and is erased from the bundle, so it cannot change howgetMatchingFullScreenRoutesees the route or fix the reported backdrop flicker when opening the Supplier RHP.Useful? React with 👍 / 👎.
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.
from Alex's Claude agent
You are right — the
backToaddition is TS-only, cannot change runtime linking behavior. Closing this PR. Will reopen once I have a proper local repro to identify the actual runtime cause of the backdrop rebuild.