2 ms·
Trying to prevent phishing, and hiding the URL such that you only see it with an explicit action, are two separate things. The first makes sense, but it by no m
by eridius 13y ago
Trying to prevent phishing, and hiding the URL such that you only see it with an explicit action, are two separate things. The first makes sense, but it by no means requires the second. iOS is a perfect example. Everyone talking about this says how iOS 7 does the same thing. Except it doesn't. You cannot interact with the URL bar, say, to search for something else, without first making the URL visible. And that's fine. But this Chrome experiment doesn't do that. It makes it so you can trivially search without ever seeing a URL. And that's the part I disagree with.
If you want to experiment with making phishing obvious, you can play with much more obvious separations between domain and path. I see no reason why you can't use the same origin chip that's being experimented with now, but simply show the rest of the URL in the field next to the origin chip. You could even hide the URL until the user interacts with the bar, the same way iOS 7 does, except I don't think there's any good reason to do that (that's hiding potentially-useful information with no benefit [assuming that the visual distinction between domain and path is large enough, such as it is with this new origin chip]).