-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
A option which can turn off the path hover in the VSCode file explorer #207796
Comments
We don't plan to allow turning off the hover, but are aiming to make the hover more useful for the explorer |
I'm sad about this decision because I try to hide almost all the elements inside my editor, making it as minimalistic as possible. If you can make the hover more useful, that would be great, but for me, it will most likely remain an annoying element that interferes with concentration. I'm providing a way to disable this feature for those who resonate with my perspective. You'll need to install an extension that lets you inject your own CSS rules. I use Custom CSS and JS Loader. Open Developer Tools to run the script provided below. This script will target the hover and all its parent elements: // The time in milliseconds you have to move the cursor from Developer Tools to
// Explorer to display the hover-element.
const time = 3000
// The content that will be displayed inside the hover-element.
const text = "~/opensubtitlescli/rest/languages.go"
function main() {
console.log(`Searching for "${text}" in ${time}ms...`)
setTimeout(search, time)
}
function search() {
let done = false
let el = document
.evaluate(`//*[text()="${text}"]`, document, null, XPathResult.ANY_TYPE, null)
.iterateNext()
if (el === null) {
console.error(`Could not find "${text}"`)
done = true
}
while (!done) {
console.log(el)
el = el.parentElement
if (el === null) {
done = true
}
}
}
main() You can create a CSS rule to hide the hover based on the elements obtained. Here's what I came up with: .monaco-workbench .context-view .hover-contents {
display: none !important;
} My VSCode VersionVersion: 1.87.2 |
If you find the hovers in the workbench annoying you can increase the delay after which the hover is shown with the |
Referring to
I don't require any extra information and this is my point. The content in Explorer provides me with all the information I need. Maybe some might find it useful to display something in this hover, my preference is to hide it. |
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Please add this feature. ( I am running code server b.t.w. ) |
I am assuming you meant "Workbench > Hover: Delay" |
Thank you so much for this. On FF, these hover tips are essentially a bug because of their strange positioning offset and stickiness (sometimes they remain visible until the browser window loses focus completely). For any others experiencing this: I'm using the FF 'Stylus' extension which let me drop this CSS in. I think this shows how unnecessary this path hover tips are in the first place. |
That's also my approach. Therefore every setting that can turn off things is welcome, like turning off the path hover in file explorer. |
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
all the popups from mouse hovering are too distracting and serve very little purpose after seeing it the first time. There are hover tooltips on every single window element except the slide bar. its basically clippy |
Hi, I'd like to revisit issue #173236 regarding a feature awaited by many. It was previously in progress (see #174085) but was closed by the author, even though @lramos15 was keen on its implementation. I believe it's worth giving this feature another shot. Thanks.
#174085
#173236
#115653
#82775
#70768
The text was updated successfully, but these errors were encountered: