Repository navigation
feat(web): expose support conversation context - #6727
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d2409431cc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| } | ||
| webViewClient = BottomSheetWebViewClient() | ||
| if (isCustomerServiceUrl(this@WebBottomSheetDialogFragment.url)) { | ||
| addJavascriptInterface(SupportWebAppInterface(context), "MixinContext") |
There was a problem hiding this comment.
When the support page embeds an iframe or follows a normal HTTP(S) link, this JavaScript interface remains exposed because BottomSheetWebViewClient allows every HTTP(S) URL to load in the same WebView and the bridge is removed only during destruction. Such third-party content can therefore call MixinContext.getContext() and obtain the user's stable, account-derived support conversation identifier. Restrict HTTP(S) navigation to the customer-service origin or remove/use an origin-scoped bridge before loading any other origin.
Useful? React with 👍 / 👎.
2 participants
No description provided.