-
Notifications
You must be signed in to change notification settings - Fork 38.4k
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberIssue has been confirmed by VS Code Team memberfirefoxIssues running VSCode in Web on FirefoxIssues running VSCode in Web on Firefoxgood first issueIssues identified as good for first-time contributorsIssues identified as good for first-time contributorshelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunitiesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersunder-discussionIssue is under discussion for relevance, priority, approachIssue is under discussion for relevance, priority, approachupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeededwebIssues related to running VSCode in the webIssues related to running VSCode in the webworkbench-auxwindowIssues related to use of auxiliary ("floating") windows.Issues related to use of auxiliary ("floating") windows.
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes/No
- VS Code Version: 1.103.0-insider
- OS Version: Ubuntu 24.04
Steps to Reproduce:
- Go to https://vscode.dev on the latest version of Firefox
- Create a new unamed test file
- Right click on the tab title, then
Copy in new window - Open the command picker, type
color themethen selectPreferences: Color Theme - While the external window is still visible, change the theme to a white theme
- In the external window, the theme is partially applied and looks completely broken
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfirmedIssue has been confirmed by VS Code Team memberIssue has been confirmed by VS Code Team memberfirefoxIssues running VSCode in Web on FirefoxIssues running VSCode in Web on Firefoxgood first issueIssues identified as good for first-time contributorsIssues identified as good for first-time contributorshelp wantedIssues identified as good community contribution opportunitiesIssues identified as good community contribution opportunitiesinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code Insidersunder-discussionIssue is under discussion for relevance, priority, approachIssue is under discussion for relevance, priority, approachupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)verifiedVerification succeededVerification succeededwebIssues related to running VSCode in the webIssues related to running VSCode in the webworkbench-auxwindowIssues related to use of auxiliary ("floating") windows.Issues related to use of auxiliary ("floating") windows.