Repository navigation
fix: Text Comparer not showing any diff on macOS and Linux - #1689
Merged
Merged
Conversation
Contributor
Author
|
I confirm that this is a bug that needs fixing. It would be good if the maintainers review this PR. |
veler
approved these changes
Sep 29, 2026
veler
left a comment
Collaborator
There was a problem hiding this comment.
Hello, this is awesome, thank you very much, and sorry for the late answer!
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.


Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number: #1296 #1623 #1562 #1541
On macOS and Linux, the Text Comparer shows both panes but never renders any
+/-highlighting. Monaco editor computes diffs in a web worker, and labels that worker with a URL fragment:macOS (WKWebView) and Linux (WebKitGTK) are both WebKit, and WebKit passes the fragment to the custom scheme handler. Both platforms carried the same
RemovePossibleQueryString, which cut the URL at?but not at#, so the file lookup missed and the worker received Blazor's placeholder text as its script:No worker means no diff computation, so no decorations. Windows is unaffected because WebView2 is Chromium and doesn't pass the fragment to its resource handler.
What is the new behavior?
There is no content at …Verified on macOS 26.5 arm64 and Ubuntu 26.04.
Other information
Quality check
Before creating this PR: