Conversation
|
@aeschli as for breaking web API, I suggest to give John Keech a ping either in an issue or via chat, in the end Codespaces is the only external consumer of our API so far. Not sure they would actually leverage any theming related embedder API we have, other than setting the default theme. |
|
In places like these: export const ACTIVITY_BAR_BORDER = registerColor('activityBar.border', {
dark: null,
light: null,
hcDark: contrastBorder
}, localize('activityBarBorder', "Activity bar border color separating to the side bar. The activity bar is showing on the far left or right and allows to switch between views of the side bar."));Shouldn't we also set a default for |
Yes, this is the task |
|
Awesome, thanks so much for getting this going! Working on my items today/early next week. |
|
Seeing this warning after adding values for vscode/extensions/git/package.json Lines 2278 to 2288 in 502276a |
Pushed a fix |
|
Finished my tasks. Let me know if anything looks off 🙏 I'll update the letterpress assets in distro as well once this is in. |
| @@ -36,10 +36,12 @@ | |||
| animation: monaco-findInput-highlight-1 100ms linear 0s; | |||
| } | |||
| .hc-black .monaco-findInput.highlight-0 .controls, | |||
There was a problem hiding this comment.
Looks like there are still hard coded colors in findInput.css that we should externalize.
hcLight uses the same color as hcDark, is that intended?
There was a problem hiding this comment.
Fixed so that hc-light uses the light colors/animations. Thansk for catching that.
As for the hard coded bits, are you referencing the disabled background rules and the animation backgrounds? I'd need to go decide on specific colors for each theme if all of them have been using the same values all this time. Might make sense to do this on a separate issue since it goes beyond HC.
| iconClass = iconClassGenerator.nextId(); | ||
| dom.createCSSRule(`.${iconClass}`, `background-image: ${dom.asCSSUrl(iconPath.light || iconPath.dark)}`); | ||
| dom.createCSSRule(`.vs-dark .${iconClass}, .hc-black .${iconClass}`, `background-image: ${dom.asCSSUrl(iconPath.dark)}`); | ||
| dom.createCSSRule(`.vs-dark .${iconClass}, .hc-black .${iconClass}, .hc-light .${iconClass}`, `background-image: ${dom.asCSSUrl(iconPath.dark)}`); |
There was a problem hiding this comment.
Shouldn't hc-light use iconPath.light(if available)
|
Thanks a lot @daviddossett ! |
|
Added mising registrations. Thanks for the tip on removing the type 👍 |
|
I made a search to
|
|
Merging the PR so we get more testing. |
Thanks—will take a look and fix as needed |
|
FYI I updated the letterpress assets in distro to match the new naming scheme e.g. Fixed missing or wrong class additions in 74157b3 |
Fixes #144193
ColorScheme.HIGH_CONTRAST_LIGHT(valuehcLight), renamedColorScheme.HIGH_CONTRAST(old valuehc), toColorScheme.HIGH_CONTRAST_DARK(new valuehcDark)ColorScheme.isHighContrastto test if the current theme is a high contrast themehcDarkandhcLight.hcLightis currently optional and uses eitherhcDarkif it isnullor color id elselightif it is a color valuehcLightin all the registrations (let me know if I can help)hc-lighthcLightishc-light(ForhcDarkit ishc-black, as beforeletterpress-hcDark.svg)preferredHighContrastLightColorThemedefaults.highContrastLightlighthighContrastis not renamed to not break any existing userswalkthroughscontribution point: new optional propertysteps.media.image.hcLighthighcontrasticons for both hc light and dark (to be reconsidered) (see here)ColorScheme.HIGH_CONTRAST_LIGHT(valuehcLight), renamedColorScheme.HIGH_CONTRAST(old valuehc), toColorScheme.HIGH_CONTRAST_DARK(new valuehcDark)(@bpasero speak up if we must not break the web API)