Skip to content
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

headless mode and functions limited #2685

Open
Julian-Eslava opened this issue Jan 12, 2025 · 2 comments
Open

headless mode and functions limited #2685

Julian-Eslava opened this issue Jan 12, 2025 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@Julian-Eslava
Copy link

-->

Environment (please fill in the following information): **

  • Operating System (e.g., Windows 10): Windows 10 Professional (X64) 22H2
  • Extension version (e.g., 1.2.3): v2.1.6

Describe the error:

  1. Error: I can't access all features because I supposedly haven't disabled it when that's not true.
  2. Error: I can't create variables from the DevTools; I get a notification and then an error about not finding a file.

Steps to playback:

  1. Error: I open the browser in any way and it always appears at the top of the screen.
  2. Error: Go to DevTools in styles, hit +, create any variant and the notification appears and, when I delete it or repeat the process, the error appears.

**Expected behaviour

  1. Update once headless is disabled and it will be removed.
  2. That you can create custom variables faster.

Additional context:

Image

Image

Image
*** Translated with www.DeepL.com/Translator (free version) ***

@vidorteg
Copy link
Contributor

Hi @Julian-Eslava

Thank you for reporting this issues, here are some thoughts.

For # 1

  • I have noticed that if you use the headless version of the extension, then you close it and deactivate the checkbox for headless on the extension settings (to get a non-headless browser), sometimes the Edge process used to launch the headless version is kept alive, so the next time we try to launch it in non-headless mode it will continue using the existing headless session. A quick fix for this is, Open "Task manager" in windows and see if you have any msedge.exe process around that was kept alive and close it from there. Next time you launch from vscode it should work

For # 2
Interesting I'll take a look, thanks for reporting.

@vidorteg vidorteg added the bug Something isn't working label Jan 17, 2025
@Julian-Eslava
Copy link
Author

Thank you very much for your attention and response. About problem 1, the truth is that it didn't work for me, I did it in several ways, but it definitely didn't work for me; wouldn't it be better if the headless mode was deactivated by default in a patch so as not to have these problems?

@vidorteg vidorteg self-assigned this Jan 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants