3 ms·
Yes, Chrome's implementation is extremely buggy and is triggered by all sorts of small movements, in addition to providing terrible clues to the user about what
by epistasis 15y ago
Yes, Chrome's implementation is extremely buggy and is triggered by all sorts of small movements, in addition to providing terrible clues to the user about what is going on.
Safari's implementation is much less painful, is only triggered when I really want it, and provides sufficient visual clues about what's going on.
Chrome's blunder is almost enough for me to switch to Safari, which is saying a lot given my preference for Chrome otherwise.
- RandallBrown 15y agoI use Safari for this reason, and because it took forever for Google to get out a version that wasn't mostly broken on Lion.
- mitjak 15y agoI quite like Safari myself, save for the visible tab limit (8 or 9 on my monitor, and have to use the drop down on right hand side to get to other tabs; what year is this?!) and no favicons. Do you or anyone else happen to know of any remedies for those?
- _frog 15y agoA suite of Safari extensions/hacks known as Glims[1] adds favicons to tabs among other things, not sure about allowing more than 8 or 9 tabs though. [1]: http://machangout.com/ http://machangout.com/