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

Issue Reporter: UX issues #42856

Closed
kieferrm opened this issue Feb 3, 2018 · 1 comment
Closed

Issue Reporter: UX issues #42856

kieferrm opened this issue Feb 3, 2018 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@kieferrm
Copy link
Member

kieferrm commented Feb 3, 2018

Issue Type

Bug

Description

The issue reporter has several issues that we should address:

  • When working is more than one display the issue reporter opens always on the primary display. If the workbench window is on the secondary display, this causes the issue reporter to be invisible.
  • The issue reporter window is always on top of the workbench window. This is an issue on smaller displays.
  • The issue reporter is slightly too large on initial layout. This causes the "Preview on GitHub" issue to be scrolled out of the viewport.
  • We use a fwlink. This link is length restricted to a degree that makes the issue reporter hard to use.

VS Code Info

VS Code version: code-oss-dev 1.21.0 (Commit unknown, Date unknown)
OS version: Darwin x64 16.7.0

Reproduces without extensions

@kieferrm kieferrm added the bug Issue identified by VS Code Team member as probable bug label Feb 3, 2018
@kieferrm kieferrm added this to the January 2018 milestone Feb 3, 2018
RMacfarlane pushed a commit that referenced this issue Feb 3, 2018
* Open issue reporter in same display as workbench

* Styling updates

* Increase url length limit

* normalize extension ids before checking isEnabled
@chrmarti
Copy link
Contributor

chrmarti commented Feb 5, 2018

Verified all except the links length issue for which I'll reopen #42603.

@chrmarti chrmarti added the verified Verification succeeded label Feb 5, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

3 participants