Forum Discussion
Ask Before Closing Multiple Tabs feature - Now Available
I can somewhat understand why Omar-Os wants to have the number of open tabs shown in the warning. I totally respect that different browsers do things differently, but as someone who is also migrating from Firefox, I was actually also expecting the warning to warn me about not only that I'm going to close all tabs but also how many tabs I'm going to close. Of course this feature is not supposed to count the number of open tabs, but I don't thnk showing the number in the warning would be misplaced or could have any negative impact on the user experience either. It might actually even improve the user experience in my opinion.
Omar-Os Maybe the Extension Tab Count for Microsoft Edge is useful to you as an alternative.
so any real life example or use cases for it that is useful?
HotCakeX wrote:sure, and then we're back at this 😉
But I already explained that: It is not useless because it makes the user aware of what is precisely going to happen. Telling the user how many tabs will be closed is a more concrete information than just telling that all tabs will be closed.
But anyways, we seem to have different opinions on that, which is of course totally fine. I just wanted to make sure that you understand my point and why I think this additional information could be considered as useful by users.
- Spoiler
-Mohit- wrote:
HotCakeX wrote:
Yes, I think the number of tabs can be shown somewhere else and would be useful,
and then i think there will be other complications, whether that number should represent tabs in other windows, other windows themselves, PWAs, tabs in PWAs, Application guard Window, Edge windows on other virtual desktops (Windows 10) etc.Good point. Considering this, it would make even more sense to put the number in the closure warning and not somewhere else, because that clearly references only the window to be closed 😉
sure, and then we're back at this 😉
I don't really care who sends what suggestion using feedback button, but in the public thread here, and based on my experience with Firefox, I don't see any use for it, because of the reasons in the comment above.
but if you find it useful then that's good, send feedback about it ^^
p.s There are TONS of other ideas posted by others in the community that I LOVE them to be implemented.
HotCakeX wrote:
Yes, I think the number of tabs can be shown somewhere else and would be useful,
and then i think there will be other complications, whether that number should represent tabs in other windows, other windows themselves, PWAs, tabs in PWAs, Application guard Window, Edge windows on other virtual desktops (Windows 10) etc.Good point. Considering this, it would make even more sense to put the number in the closure warning and not somewhere else, because that clearly references only the window to be closed 😉
- Yes, I think the number of tabs can be shown somewhere else and would be useful,
and then i think there will be other complications, whether that number should represent tabs in other windows, other windows themselves, PWAs, tabs in PWAs, Application guard Window, Edge windows on other virtual desktops (Windows 10) etc. HotCakeXWell, it might improve the user experience because it makes users a bit more aware of what they are going to do.
For example, I noticed that when I close a Firefox window with a huge number of open tabs (rather than one with a small number) I often consider checking once more if there is really no important tab among them. That's why I find a message like "Do you want to close 123 tabs?" more helpful than a message like "Do you want to close all tabs?".
Of course, this may be completely subjective and only my personal preference. I can't tell what other users find useful or not.
And besides, Edge doesn't (natively) show the number of open tabs anywhere else either, right? It does however in the mobile Version. So this feature could be a way to introduce this information in the Desktop version.
By the way, I'm not saying that this is an essential information or that the closure warning feature would be inclomplete without it. It doesn't even necessarily have to be in the closure warning message (but it would make sense though).
