I want to be asked before closing multiple tabs
Reported by
drawmap2...@gmail.com,
Nov 1 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Steps to reproduce the problem: 1. Open multiple tabs 2. Click the X to close 3. This is where I want to be asked to confirm What is the expected behavior? I would either like to be able to set a preference to not close multiple tabs, or at least be prompted before they are closed. Both IE and Firefox do this. What went wrong? See above Did this work before? No Chrome version: 52.0.2743.82 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 27.0 r0
,
Nov 1 2017
See issue 147
,
Nov 1 2017
,
Nov 2 2017
As per comment #3, as this is marked as Feature request, changing the status to 'Untriaged' for further updates from Dev. Thanks..
,
Nov 10 2017
,
Nov 10 2017
,
Nov 10 2017
We've discussed this UI in the past. Because Chrome provides the ability to undo tab closure, confirmation prompts before closing are less critical. Additionally, prompts train people to click through them as part of the process of closing tabs, meaning that they often don't save you when you realize you wanted to keep a tab open (because of reflexively clicking "yes"). Finally, we wouldn't prompt by default, and Chrome's design philosophy of not adding options unless absolutely necessary precludes adding this as an option. The one behavior I wouldn't necessarily mind seeing is some sort of transient "press ctrl-shift-t to reopen this tab" reminder the first few times you close a tab, to teach people about that feature/shortcut.
,
Nov 10 2017
I think another area that could be improved here is restoring works on a per tab basis. So, even though it's possible to close multiple tabs at once they are not restored as a group. I suspect there is a bug on this.
,
Nov 10 2017
Yeah, hitting ctrl-shift-t after a single mass-close event should mass-restore. I suspect you're right that there's a bug on this somewhere. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 Deleted