fix: block F5/Refresh in chat webview to prevent blank screen#558
Open
laileni-aws wants to merge 4 commits into
Open
fix: block F5/Refresh in chat webview to prevent blank screen#558laileni-aws wants to merge 4 commits into
laileni-aws wants to merge 4 commits into
Conversation
3dc6542 to
fee958e
Compare
fee958e to
122444c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
When the Amazon Q Chat view has focus and the user presses F5 (or triggers a browser refresh via Cmd+R / context menu), the entire chat UI disappears and is replaced by a blank white screen. The chat does not recover without manually closing and reopening the view.
Prevents the chat webview from going blank when the user accidentally triggers a browser refresh (F5, Cmd+R, or context menu reload).
The chat webview uses
browser.setText(html)to render content inline with no backing URL. A refresh causes the browser to navigate to about:blank, wiping the UI entirely.Fix:
LocationListenerthat blocks any navigation toabout:blank, preventing the blank screen regardless of how the refresh is triggered.KeyListenerthat intercepts F5 keypress and suppresses it as an additional safeguard.Testing:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.