Opening Find in an unrelated webview activates vscode-R and shows `R: (not attached)` in non-R workspaces
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Tranquilla
- Stack tecnologico
- typescript, vscode
- Ambito
- developer-experience, tooling
Direzione di ricerca
Inizia da package.json e dai contributi del menu editor/title per editor.action.webvieweditor.showFind, quindi riproduci l’attivazione da un’anteprima Markdown usando la scorciatoia Find indicata. Controlla exthost.log per l’evento di attivazione; il lavoro è completato quando un webview non correlato non attiva più vscode-R né mostra R: (not attached), mentre i webview R mantengono la loro azione Find.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Describe the bug
The R extension activates and shows its session status bar item R: (not attached)
even in a workspace with no R files, simply because I triggered the Find widget
in an unrelated webview, such as a Markdown preview.
On my Windows machine, R itself is not installed at all — I only installed the
vscode-R extension. That alone is enough for R: (not attached) to show up once Find
is opened in an unrelated webview, so this is purely about extension activation, not
about any R file, R session, or R runtime.
The likely trigger is that package.json contributes the built-in command
editor.action.webvieweditor.showFind (titled "R: Find in WebView"). This command is
then used in editor/title menus gated by r.browser.active / r.helpPanel.active.
Since VS Code 1.74.0, a command contributed in package.json implicitly activates the
extension when that command is invoked. Because editor.action.webvieweditor.showFind
is the shared built-in webview Find command, invoking Find in any webview
(Markdown preview, release notes, etc.) activates vscode-R, not just R's own
help/browser panels.
Confirmed in exthost.log:
ExtensionService#_doActivateExtension REditorSupport.r, startup: false,
activationEvent: 'onCommand:editor.action.webvieweditor.showFind'
To Reproduce
- Open a folder that contains no R-related files (
.R,.Rmd,.Rproj, etc.). - Open a webview-based editor with a Find widget, e.g. a Markdown preview.
- Focus that preview and press
Cmd+Fon macOS /Ctrl+Fon Windows or Linux.
In my environment, this invokes the built-ineditor.action.webvieweditor.showFind. - The vscode-R extension activates and
R: (not attached)appears in the status
bar, despite no R file or R session being present. It stays visible until the
window is reloaded.
I have reproduced this on both macOS (Cmd+F) and Windows (Ctrl+F), so it does
not appear to be platform-specific.
Can you fix this issue by yourself? (We appreciate the help)
No, but I am happy to test a fix or provide more logs.
(If yes,) can we assist you with anything?
N/A
(If applicable) Please attach setting.json
On macOS, the only R setting I customized is:
"r.rpath.mac": "/usr/local/bin/R"
r.sessionWatcher is left at its default value, true.
On Windows, my settings.json has no r.* keys at all, and R is not installed.
Only the vscode-R extension is present. The bug still reproduces.
Expected behavior
The extension should not activate, and the session status bar item should not appear,
merely because Find was opened in an unrelated webview.
The "R: Find in WebView" action should be scoped to R's own webviews only, without
contributing the shared built-in webview Find command id in a way that causes global
activation from unrelated webviews.
Possible approaches:
- avoid contributing the built-in command id
editor.action.webvieweditor.showFind
directly incontributes.commands; - use a vscode-R wrapper command that is only exposed for R webviews and internally
calls the built-in Find command; - or hide the session status bar item unless an R-related editor, workspace, session,
or webview is actually relevant.
This seems related in spirit to #1572 / #1579, where R UI was made conditional so it
does not appear in unrelated workspaces.
Screenshots
The status bar shows R: (not attached) in a workspace with no R files. I can attach
a screenshot if useful.
Environment (please complete the following information):
- OS: reproduced on both macOS and Windows
- VS Code Version: 1.122.1
- R Version: N/A — reproduces with no R session involved. On Windows, R is not even
installed; only the vscode-R extension is present. - vscode-R version: 2.8.8
Additional context
When r.sessionWatcher is enabled, which is the default, activation creates and shows
the session status bar item. Therefore, once vscode-R is activated by the unrelated
webview Find command, R: (not attached) remains visible for the rest of the window
session, even though the current workspace/editor is unrelated to R.
- Lingua principale
- TypeScript
- Stelle
- 1.2k
- Fork
- 139
- Merge medio
- 16h 16m
- PR unite (30g)
- 11
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di REditorSupport/vscode-R
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
REditorSupport/vscode-R#1687 · 4 commenti · 3 reazioni ·
-
feature-request
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
REditorSupport/vscode-R#1763 ·
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 65/100
REditorSupport/vscode-R#1756 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
REditorSupport/vscode-R#1755 · 2 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
REditorSupport/vscode-R#1751 · 1 commento ·
Tutte le issue di REditorSupport/vscode-R
Issue simili
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
motiondivision/motion#3849 ·
-
Add: S Play Event HD Apertacheck:passed streams:add
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
LiteLLM proxy response_cost (x-litellm-response-cost) is never applied to ChatModelOutput.cost Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
i-am-bee/beeai-framework#1697 · 1 reazione ·
-
Support bun dedupe Apertaenhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
antfu/node-modules-inspector#214 ·