镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

Reload instead open recent #7384

Description

@Tealk

Is there an existing issue for this?

  • I have searched the existing issues

OS/Web Information

  • Web Browser: Ungoogled Chromium
  • Local OS: Fedora
  • Remote OS: Debian
  • Remote Architecture: amd64
  • code-server --version: 1.100.3 409c64e x64

Steps to Reproduce

  1. Open Webside
  2. Use STRG+R

Expected

recent open without page reload

Actual

recent open and page reloads

Logs

Screenshot/Video

Image

Does this bug reproduce in native VS Code?

This cannot be tested in native VS Code

Does this bug reproduce in GitHub Codespaces?

No, this works as expected in GitHub Codespaces

Are you accessing code-server over a secure context?

  • I am using a secure context.

Notes

No response

Activity

  1. added
    bugSomething isn't working
    triageThis issue needs to be triaged by a maintainer
    on Jun 20, 2025
  2. code-asher commented on Jun 20, 2025

    @code-asher
    Member

    Hmm for me it is working (it opens a menu and does not reload). I tried both Chromium and Firefox. I wonder if it could be related to keyboard layout, but if it works in Codespaces I would expect it to work with code-server as well.

    Do you have any errors or warnings in the browser console?

  3. Tealk commented on Jun 21, 2025

    @Tealk
    Author

    Als Brwoser nutze ich die Flatpak version, aber heute scheint der Fehler nicht mehr aufzutreten. Der Browser hat aber kein Update bekommen soweit ich sehen kann.

    Das ist die console beim aufruf:

    Fetch event handler is recognized as no-op. No-op fetch handler may bring overhead during navigation. Consider removing the handler if possible.
    log.ts:440  INFO Resolving connection token (code.rollenspiel.network)...
    log.ts:440  INFO Resolved connection token (code.rollenspiel.network) after 9 ms
    log.ts:440  INFO Creating a socket (renderer-Management-ee55d3b7-a357-496b-af52-28070356cb9c)...
    log.ts:440  INFO Creating a socket (renderer-Management-ee55d3b7-a357-496b-af52-28070356cb9c) was successful after 53 ms.
    /stable-409c64e0df4d53530e59c16acc2b5d5766f717b0/static/node_modules/vsda/rust/web/vsda_bg.wasm:1 
                
                
               Failed to load resource: the server responded with a status of 404 ()
    /stable-409c64e0df4d53530e59c16acc2b5d5766f717b0/static/node_modules/vsda/rust/web/vsda.js:1 
                
                
               Failed to load resource: the server responded with a status of 404 ()
    webWorkerExtensionHost.ts:116 The web worker extension host is started in a same-origin iframe!
    C @ webWorkerExtensionHost.ts:116
    log.ts:440  INFO Creating a socket (renderer-ExtensionHost-2a76e4da-01e9-4ff6-a14a-505073c348a8)...
    Error with Permissions-Policy header: Unrecognized feature: 'ambient-light-sensor'.
    Error with Permissions-Policy header: Unrecognized feature: 'battery'.
    Error with Permissions-Policy header: Unrecognized feature: 'document-domain'.
    Error with Permissions-Policy header: Unrecognized feature: 'execution-while-not-rendered'.
    Error with Permissions-Policy header: Unrecognized feature: 'execution-while-out-of-viewport'.
    Error with Permissions-Policy header: Unrecognized feature: 'navigation-override'.
    Error with Permissions-Policy header: Unrecognized feature: 'web-share'.
    Error with Permissions-Policy header: Unrecognized feature: 'speaker-selection'.
    webWorkerExtensionHostIframe.html:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
    [Violation] Potential permissions policy violation: usb is not allowed in this document.
    [Violation] Potential permissions policy violation: cross-origin-isolated is not allowed in this document.
    log.ts:440  INFO Creating a socket (renderer-ExtensionHost-2a76e4da-01e9-4ff6-a14a-505073c348a8) was successful after 121 ms.
    log.ts:450  WARN [redhat.vscode-yaml]: Cannot register 'redhat.telemetry.enabled'. This property is already registered.
    warn @ log.ts:450
    TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.yaml.
    Old grammar file: vscode-remote://code.rollenspiel.network/usr/lib/code-server/lib/vscode/extensions/yaml/syntaxes/yaml.tmLanguage.json.
    New grammar file: vscode-remote://code.rollenspiel.network/home/tealk/.local/share/code-server/extensions/redhat.vscode-yaml-1.18.0-universal/syntaxes/yaml.tmLanguage.json
    register @ TMScopeRegistry.ts:46
    TMScopeRegistry.ts:46 Overwriting grammar scope name to file mapping for scope source.yaml.
    Old grammar file: vscode-remote://code.rollenspiel.network/usr/lib/code-server/lib/vscode/extensions/yaml/syntaxes/yaml.tmLanguage.json.
    New grammar file: vscode-remote://code.rollenspiel.network/home/tealk/.local/share/code-server/extensions/redhat.vscode-yaml-1.18.0-universal/syntaxes/yaml.tmLanguage.json
    register @ TMScopeRegistry.ts:46
    console.ts:137 [Extension Host] Added a "Run Ansible Playbook" command...
    console.ts:137 [Extension Host] Added a "Run with Ansible Navigator" command...
    console.ts:137 [Extension Host] Created roles cache for /home/tealk/ansible/roles
    console.ts:137 [Extension Host] Created roles cache for /etc/ansible/roles
    console.ts:137 [Extension Host] tox workspace folder: /home/tealk/ansible
    log.ts:440  INFO [Service Worker] registered
    console.ts:137 [Extension Host] Reinitialized extension settings
    console.ts:137 [Extension Host] Ansible found in the workspace
    log.ts:440  INFO Updating additional builtin extensions cache
    4console.ts:137 [Extension Host] Ansible found in the workspace
    
  4. code-asher commented on Jun 23, 2025

    @code-asher
    Member

    Strange, not sure what would cause it. I will go ahead and close the issue if it is not happening anymore, but feel free to comment if you find a way to reproduce.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtriageThis issue needs to be triaged by a maintainer

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions