5 ms·
I do give it a chance, regularly, but it's never enough to be 'default'. Pins. Loved the idea. Unfortunately, they often go missing. Loading the browser, ab
by mgkimsal 7y ago
I do give it a chance, regularly, but it's never enough to be 'default'.
Pins. Loved the idea. Unfortunately, they often go missing. Loading the browser, about 15% of the time, I get the "oh this is embarrassing" screen, with "restore your session". If I don't restore right then, all pins are gone. For good. Forever. I've lost way too much time recreating those over the last couple of years.
Have never had this happen ever in Chrome. I can't say it never happens in Chrome ever - maybe for someone it has - but not for me. However, I don't even know how to report this. "My pins get lost". If they're just special tabs, and tabs are known to get lost, is this even a 'bug'? Or just... "I'm doing it wrong" (as in, expecting pins to be more useful than they are?)
- TazeTSchnitzel 7y agoThe “restore your session” shouldn't be regularly appearing when you start the browser and indicates it's crashing on shutdown or otherwise failing to save state. That is a bug.
- mgkimsal 7y agothis has happened to me fairly regularly, for years, on multiple different pieces of hardware/cpu/drives, under different user profiles, ISPs, and operating systems. 15% may have been a high estimate - probably under 8-10% of the time starting up. But it's enough to mean I just can't trust it as much as I can trust other platforms.
- WaltPurvis 7y agoIn Chrome, a pinned tab will close when you hit Cmd-W, which is never what I want to happen. E.g., I have Gmail pinned, I open several more tabs, then at some point type Cmd-W several times to close those tabs, but if I type one extra Cmd-W my Gmail tab goes away (and the window closes). Again, I never want pinned tabs to be closed that way. The whole idea of pinning something is to make sure it stays in place. That's what pinning means. It's really irritating (as you can probably tell).
- mgkimsal 7y agoYep. Agreed, annoying. Perhaps they'll offer some preventing of this at some point? I've noticed the "ctrl-q" quit thing recently got a "long hold" default option - which I now despise as its defaulted 'on'. :/