* Fix color values in 2026 theme JSON files to remove alpha channel
* Remove hover background color for quick input list in 2026 theme JSON files
* Update color theme settings and chat color registrations for improved visibility and consistency
* Update chat request bubble colors for improved visibility
* Enhance modern UI theming with new inactive background colors and border styles
* Add modern sash grip color support and update related styles
* Enhance theme consistency by adding panel section and header borders across multiple color themes
* Add inactive background colors for status and title bars across multiple themes
* feat(theme): enhance theme service with inactive title bar background support
refactor(activitybar): replace isInactive state with activeWindowId for focus handling
refactor(statusbar): update to use activeWindowId instead of isInactive for background color logic
refactor(titlebar): modify title bar to track activeWindowId instead of isInactive
fix(theme): improve status bar inactive background description for clarity
chore(chat): deprecate unused chat input accent colors and clarify usage
docs(modernUI): update README with details on new color IDs and their usage
test(partsSplash): add tests for parts splash colors handling based on window focus
test(chatColors): implement tests for chat color registrations and deprecations
test(titlebar): create tests for title bar color resolution based on window focus
* feat(theme): update modern sash grip foreground color for multiple themes
* feat(theme): update modern sash grip foreground color to 40% alpha for dark and light themes
* Fix activity bar inactive color test
Model the active window through TestHostService so the Electron unit test does not depend on the runner window's document focus.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Test activity bar auxiliary window focus
Verify that refocusing the host does not reactivate the main activity bar while an auxiliary window remains active.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Modern UI: Add background colors for the activity bar in various themes
* Modern UI: Update inactive activity bar background color reference and add test for inheritance
---------
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
* theme: update agent panel border colors and styles across themes
* theme: update border colors for agents in various themes
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* fix(theme): update agentsPanel.border to transparent
* fix(theme): set agentsPanel.border to transparent
* fix(screenshots): update image links for agent host and user data migration
---------
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* feat: move from yarn to npm
* chore: skip yarn.lock files
* fix: playwright download
* chore: fix compile and hygiene
* chore: bump vsce@2.17.0
Refs https://github.com/microsoft/vscode-vsce/commit/8b49e9dfdf909ad3af2b9ec9c825f5b501f6d75e
* test: update results for bat and sh colorizer tests
* fix: add missing lock files for windows
* fix: switch to legacy-peer-deps
* chore: update markdown-it@14.1.0
Refs https://github.com/markdown-it/markdown-it/commit/737c95a12976357df99652e4b51d831cac4a75aa
esbuild step in extensions-ci-pr was previously using markdown-it
from root which had userland punycode and was able to compile successfully.
* ci: increase pr timeout for windows integration tests
* chore: fix product build
* build: ignore extension dev dependency for rcedit
* build: fix working directory inside container
* build: fix dependency generation
* npm: update dependencies
* ci: use global npmrc
* ci: update cache
* ci: setup global npmrc for private npm auth
* build: fix extension bundling
* chore: sync npm dependencies
* ci: debug env variables for container
* ci: fix win32 cli pipeline
* build: fix npmrc config usage for build/ and remote/ dirs
* fix: windows build
* fix: container builds
* fix: markdown-language-features tests and bundling
```
[03:58:22] Error: Command failed: /Users/demohan/.nvm/versions/node/v20.15.1/bin/node /Users/demohan/github/vscode/extensions/markdown-language-features/esbuild-notebook.js --outputRoot /Users/demohan/github/vscode/.build/extensions/markdown-language-features
✘ [ERROR] Could not resolve "punycode"
extensions/markdown-language-features/node_modules/markdown-it/lib/index.js:14:27:
14 │ var punycode = require('punycode');
╵ ~~~~~~~~~~
The package "punycode" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
```
Adds userland package based on https://github.com/markdown-it/markdown-it/commit/beed9aee2c1b44819afc25d485e86a6c699b6ef0
* fix: container builds for distro
* chore: update yarn occurrences
* fixup! chore: bump vsce@2.17.0
Uses the closest version to `main` branch that does not
include https://github.com/microsoft/vscode-vsce/commit/d3cc84cdec99b8e9f24be63d1a2a54abe908f68b
while still having the fix https://github.com/microsoft/vscode-vsce/commit/8b49e9dfdf909ad3af2b9ec9c825f5b501f6d75e
* chore: sync npm dependencies
* chore: sync npm dependencies
* chore: sync npm dependencies
* chore: throw error when yarn is used for installation
* chore: add review feedback
* chore: switch exec => run where needed
* chore: npm sync dependencies
* fix: markdown-language-features bundling
```
✘ [ERROR] Could not resolve "punycode"
extensions/markdown-language-features/node_modules/markdown-it/lib/index.js:14:27:
14 │ var punycode = require('punycode');
╵ ~~~~~~~~~~
The package "punycode" wasn't found on the file system but is built into node. Are you trying to bundle for node? You can use "platform: 'node'" to do that, which will remove this error.
```
Adds missing userland package based on markdown-it/markdown-it@beed9ae,
can be removed once we update markdown-it >= 14.1.0
* ci: rename no-yarn-lock-changes.yml
* chore: sync npm dependencies
* ci: restore no-yarn-lock-changes.yml
We can disable it in a separate PR to keep the required
checks happy and also need workflow edit perms.
* chore: sync npm dependencies
* ci: rebuild cache
* ci: fix no-package-lock-changes.yml
* chore: bump distro
* chore: rm yarn.lock files
* chore: rm yarn.lock files without dependencies
* chore: add vscode-selfhost-import-aid to postinstall dirs
* chore: bump distro
* monokai-color-theme.json: treat Python comment string blocks
...as comments too
* Update *all* themes to consider Python block string comments as comments
modified: extensions/theme-abyss/themes/abyss-color-theme.json
modified: extensions/theme-defaults/themes/dark_vs.json
modified: extensions/theme-defaults/themes/hc_black.json
modified: extensions/theme-defaults/themes/hc_light.json
modified: extensions/theme-defaults/themes/light_vs.json
modified: extensions/theme-kimbie-dark/themes/kimbie-dark-color-theme.json
modified: extensions/theme-monokai-dimmed/themes/dimmed-monokai-color-theme.json
modified: extensions/theme-monokai/themes/monokai-color-theme.json
modified: extensions/theme-quietlight/themes/quietlight-color-theme.json
modified: extensions/theme-red/themes/Red-color-theme.json
modified: extensions/theme-solarized-dark/themes/solarized-dark-color-theme.json
modified: extensions/theme-solarized-light/themes/solarized-light-color-theme.json
modified: extensions/theme-tomorrow-night-blue/themes/tomorrow-night-blue-color-theme.json
* Update all changes to use "string.quoted.docstring"
...instead of "string.quoted.docstring.multi.python", per
@aeschli's request here:
https://github.com/microsoft/vscode/pull/182162#issuecomment-1545296640
This way the comment formatting applies to *all* language quoted
docstrings, instead of just to Python.
* bring back python colorize tests
---------
Co-authored-by: Martin Aeschlimann <martinae@microsoft.com>
* Theming for dirty tabs
* Improve border for dirty tabs
1. Make it thinner
2. Add a setting to disable it
3. Use 4 colors (activeFocused, activeUnfocused, inactiveFocused, inactiveUnfocused)
4. Move part of logic
* Hot apply of setting `dirtyTabBorder`
* Rename the setting
* Add default dirty border for all themes
* 3 of the 4 colors should be derived from the one main color
* Rename `dirty` to `modified`
* Rename `modifiedActiveFocusedBorder` to `modifiedBorder`
* Add modified border color for built-in themes
* More contrast
* Applying style directly on element
* Changing only color
* Using full border
* Using existing div for border styling
* Add setting to telemetry
* Uncomment cleanup code
* tweak colors and descriptions
* 💄
