3 ms·
Wait... If a user doesn't notice a feature (when it's clearly supposed to be noticed), doesn't that mean it's placement is slightly sub-optimal? (Although I pe
by PieSquared 18y ago
Wait... If a user doesn't notice a feature (when it's clearly supposed to be noticed), doesn't that mean it's placement is slightly sub-optimal?
(Although I personally do like the placement, and the author clearly does too; just from Google's perspective, isn't it bad that the user doesn't immediately notice it?)
- there 18y agoif it's a critical feature i would say it'd be a problem, but this is something new. if you notice it, use it, if not, you're no worse off than you were before.
- woodsier 18y agoI agree to an extent but I don't think there is a better place to put it. I've noticed it, but I doubt too many people are actively using Chrome yet.
- ComputerGuru 18y agoWhy are you all assuming no one notices this feature? The improved and very productive in-line search is one of the first things I noticed about Chrome, it's just plain awesome. Anyway, the earmark of good UI is that nifty features are there when you need them, and when they manifest themselves they're helpful. Features that get in your way when they serve no purpose only serve to clutter and bloat; so props to the Chrome team on this one.
- iigs 18y agoI didn't notice it until this article pointed it out. I think its usefulness is diminished by these things: 1) The color is too faint. 2) The scrollbar widget is standard. I think this is a good thing in general but as a user you expect it to behave a certain way and don't stand around looking auditing individual pixels, especially since they didn't keep the standard title bar design and size. 3) I spend most of my time using find thinking "I hate that slash doesn't start the search here. Grr." I know that ^F has been the standard on PCs for a long time, but / is definitely my preferred way.