-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webview scrollbars are seemingly unstyleable in Insiders #213045
Comments
Looks styled still based on the colors, just different rendering |
They really don't look that similar (other than the colors are close) -- in the first the scrollbar has no corners (arrows) is much thinner, and what you can't tell in the screenshot is that it behaves just like other VS Code scrollbars in that it hides and fades based on hover/focus. While in Insiders none of those style are taking affect -- it seems |
Version: 1.90.0-insider (Universal) I see a similar issue.
A workaround is adding the following to html {
scrollbar-color: var(--vscode-scrollbarSlider-background) var(--vscode-sideBar-background);
} Adding |
This is now broken in Stable -- @isidorn can we get a fix or resolution on this, since this is a regression from existing webview behavior. |
If this is a confirmed regression, it would help to know which change caused it. We maintain a node.js based CLI tool Steps:
Thanks! |
same issue |
same issue.
But still not like before ! |
So this is a behavior change in Chrome 121 -- if And the webview's index.html sets I've opened #220121 to address this, but in the meantime, extensions can work around this by adding the following to their webview css: @supports selector(::-webkit-scrollbar) {
html {
scrollbar-color: unset;
}
} |
… in bottom part. Implemented fix from microsoft/vscode#213045 (comment)
JFYI - I see the same problem in stable now. Version: 1.92.2 (user setup) I lucked into setting |
Here is what my webview scrollbars look like in 1.89.1:
Here is what they look like in 1.90-insiders:
The text was updated successfully, but these errors were encountered: