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

Moving a pinned editor unpins it #99086

Closed
joaomoreno opened this issue Jun 2, 2020 · 7 comments
Closed

Moving a pinned editor unpins it #99086

joaomoreno opened this issue Jun 2, 2020 · 7 comments
Assignees
Labels
*as-designed Described behavior is as designed info-needed Issue requires more information from poster workbench-tabs VS Code editor tab issues

Comments

@joaomoreno
Copy link
Member

joaomoreno commented Jun 2, 2020

Testing #98019

Drag a pinned tab and drop it on a tab bar empty space. I expected it to remain pinned. 🤷

@bpasero
Copy link
Member

bpasero commented Jun 2, 2020

@joaomoreno can you clarify, do you only have 1 pinned tab? In general, moving a pinned tab after the last tab will unpin it if that last tab is unpinned.

@bpasero bpasero added info-needed Issue requires more information from poster workbench-tabs VS Code editor tab issues labels Jun 2, 2020
@joaomoreno
Copy link
Member Author

joaomoreno commented Jun 3, 2020

In general, moving a pinned tab after the last tab will unpin it if that last tab is unpinned.

You seem to distinguish between the last tab of the drop container being pinned or not, despite the fact that I'm not dropping on top of the last tab of the container, but on the container itself. As a user, this doesn't make much sense, since my perception is that I'm dragging a pinned tab onto a container, so it should remain pinned, independently of what the state of the last tab of that container is.

recording (10)

POWERED BY GIFCAP

@bpasero
Copy link
Member

bpasero commented Jun 3, 2020

Well, my argument is that you are dropping a tab after an existing tab of a tab group. Now I am in conflict: should the tab be pinned or should it be after the last tab. Pinned tabs cannot be after unpinned tabs (currently), so I can either respect the index of the tab (which I prefer) or the pinned state.

Given comments such as #99035 (comment) I think preserving the pinned state is maybe not what we should do in many cases.

@joaomoreno
Copy link
Member Author

joaomoreno commented Jun 3, 2020

Isn't a split different than a drag and drop? 🤔

@bpasero
Copy link
Member

bpasero commented Jun 3, 2020

Yeah, fair point. Again, I am preferring to preserve the index, not the pinned state here. If you drop into an empty group, I preserve pinned state.

@bpasero bpasero added the *as-designed Described behavior is as designed label Jun 3, 2020
@bpasero bpasero closed this as completed Jun 3, 2020
@joaomoreno
Copy link
Member Author

joaomoreno commented Jun 3, 2020

@bpasero 🙈

recording (11)

POWERED BY GIFCAP

Now seriously, I'm not sure the index is the thing to preserve here. Tabs are not pinned because their index is lower than the first non-pinned tab index... they are pinned because I pinned them. Their position and their state should be two independent things, right?

@bpasero
Copy link
Member

bpasero commented Jun 3, 2020

@joaomoreno well that is just how Chrome behaves. I decided to do what Safari does which allows you to easily drag/drop tabs in and out of pinning state (which is something I heard from users is good to have).

recording

I argue Chrome is artificially limiting the DND experience when a tab is pinned.

@github-actions github-actions bot locked and limited conversation to collaborators Jul 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed info-needed Issue requires more information from poster workbench-tabs VS Code editor tab issues
Projects
None yet
Development

No branches or pull requests

2 participants