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

Report issue button in a cramped spot #64345

Closed
isidorn opened this issue Dec 4, 2018 · 2 comments
Closed

Report issue button in a cramped spot #64345

isidorn opened this issue Dec 4, 2018 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@isidorn
Copy link
Contributor

isidorn commented Dec 4, 2018

Refs: #64222

I did not want to create UX issues for running extensions view, for that I simply created this item #64344

This one I only created because it feels like a minor regression

Previosuly the report issue was aligned to the right. This I personally prefered because it was not in a cramped spot with everything else on the left. And because it was using the horizontal space which we have planty in this view.

I suggest to move it back to the right.

P.S I like that we now do not show this button for every extension

screenshot 2018-12-04 at 15 40 33

@jrieken
Copy link
Member

jrieken commented Dec 5, 2018

closing as dupe of #64344. I also don't like it much but the code is a mess and it serves its purpose. Not keen on investing more into something we are going to nuke.

@jrieken jrieken added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 5, 2018
@vscodebot
Copy link

vscodebot bot commented Dec 5, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Dec 5, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 19, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants