microsoft / microsoft/vscode-edge-devtools

Moving Webview and Dev Tools to the secondary sidebar.

Open
#1,387 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement tracked
Dominant language
TypeScript
Stars
827
Forks
358
Avg merge
20h 32m
Merged PRs (30d)
10

Description

Is your feature request related to a problem? Please describe.

On screens where screen real-estate is counted,
the way current version makes webviews pop and disappear when a debugging session is launched and terminated, makes a less appealing experience as compared to, for example, in macOS, having a Split view with Vscode on one side and a browser window with devtools at the bottom on the other.

Describe the solution you'd like:

Having an option allowing the web view and the dev tools to be moved into their dedicated space in the secondary sidebar, the UI could become much more navigable and logically differenciated. That way, we would not need to move it around again and again everytime we reset debugging, which is annoying. + this would make it very similar if not identical to the dev experience we get natively.

Describe alternatives you've considered:

Keeping things as such, even though they're not ideal for me, since edge dev tools are so amazing. 🙃

Additional context:

Here is how my setup looks usually:
Screenshot 2023-03-01 at 17 18 31

And trying to replicate something similar in VS code:

Screenshot 2023-03-01 at 17 23 58

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the extension's existing webview and DevTools placement in the VS Code UI, using the screenshots as the intended layout reference. Define how an option for the secondary sidebar should keep both surfaces available across debugging resets; done means the placement is navigable and does not require repeated manual moves.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
desktop, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.