microsoft / microsoft/vscode-edge-devtools

Comfort with default resolution and working space

Open
#2,686 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

-->

Comfort

  1. I hate it when the browser is always set to responsive because, as the space I have is so small, it is very impractical and if I set a resolution manually, then with certain actions, like switching tabs with Alt + Tab, it resets to Responsive and if I set another of the default resolutions, like Laptop with HiDPI screen, then it also resets back to Responsive.
  2. I run the browser on the right side of my screen, with the DevTools below it and the rest of the files on the left side with the CSS below. The problem is that it is very annoying that, if I am going to upload the CSS, the DevTools has to be uploaded, which consequently takes space away from the browser; it is not possible to separate the working environment between the fixed and the flexible.

**Accessibility

  1. I want to be able to add a resolution of mine of, say, 1800x820 and whenever I open the browser it defaults to that resolution.
  2. Well, what I want is to be able to move my CSS quietly without moving my DevTools and vice versa, for convenience, like dividing my workspace into two parts: what moves and what is fixed and can't be moved.

Describe the alternatives you have considered: **

  1. When you go to the Edge launch.json, that in the add configuration part there is also one that says add new default resolution configure it and modify it if you want it to default or not (and also that the launch.json is improved; I tried to do it on my own, but I couldn't, it's very unintuitive).
  2. It could be done again in the launch.json that you can add a custom space only for the extension that this space is absolute and can not be moved from there to move the rest of things quietly and, for example, with the console, that instead of the rest of the content is adapted to give space to the console, that the console overlaps them and the content is there, but under the console.

Thanks for reading me and sorry for putting two issues in one. Hopefully solutions will be given to these suggestions to make Edge a better extension for all people. :)

Additional context:

Image

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

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 Edge launch.json configuration mentioned in the issue and the extension entry points that handle default resolution and workspace layout. Clarify and separate the two requested features before implementation: persistent custom resolution and independently movable or fixed workspace panels. Done requires agreed behavior and validation for both workflows.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
desktop, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.