11–20 of 211 posts
A native breadcrumbs display might be a great addition to this. I mean, show the domain first, and show a subsection that the website provides, so I can click on that to navigate. If I click on the domain name, provide a standard url input field. Google already does that with search results: http://d.ekin.io/bOdk
EDIT: And given the seeming confusion by some, no, the "article" (if a couple of screenshots and some guy giving an opinion is an "article") is utterly irrelevant to this comment. Noting that it mentions iOS is meaningless. We continually see front-pagers voted up by people who seem blissfully unaware of trends in the industry.
As a member of the Chrome security team and one of the original instigators for this experiment, yes the whole point is to prevent phishing. The fact is that phishing is one of the most common attack vectors for most people, and the way the URL is currently displayed does very little to protect them. So, we're experimenting with ways of displaying the essential information (origin and TLS state) as clearly as possibl…
Surprised to see so much attention to this: Isn't it exactly what Safari on iOS does on hundreds of millions of devices worldwide? EDIT: And given the seeming confusion by some, no, the "article" (if a couple of screenshots and some guy giving an opinion is an "article") is utterly irrelevant to this comment. Noting that it mentions iOS is meaningless. We continually see front-pagers voted up by people who seem bliss…
A native breadcrumbs display might be a great addition to this. I mean, show the domain first, and show a subsection that the website provides, so I can click on that to navigate. If I click on the domain name, provide a standard url input field. Google already does that with search results: http://d.ekin.io/bOdk
That'd be great. But so few URLs are breadcrumbable, in fact, I should fix this on my own site, http://jakearchibald.com/2014/ is a 404.
In any case, I believe breadcrumbs should be parsed from the page html: https://support.google.com/webmasters/answer/185417?hl=en
I just hope it will still be easy to prepend urls, such as when entering reddit.com/s/URL_OF_CURRENT_PAGE
As the article states, this is likely good for the non-tech-savvy people, but what it needs is a button to copy the URL as easily. If the problem is misleading subdomains, would some kind of a detection and a warning be a better solution to the problem?
Did not try it, but apparently if you click on the domain label, it provides a standard url field so you can copy / modify the url.
An alternative would be highlight the domain portion of the URL in the appropriate color, ala source code highlighting. This would accomplish both goals nicely.
I don't get the benefit to cutting off the rest of the protocol handler and path. It may be noisy and not useful to the average user, but it's useful for people who know what they're looking at. An alternative would be highlight the domain portion of the URL in the appropriate color, ala source code highlighting. This would accomplish both goals nicely.
Even if 80% of the time I was trying to be phished, I'd still want the URL. Why? Because the URL is my ownership of the web. It's my address book. It's what domain owners pay to have. It's the roads that connect one spot to another.
So sure, phishing is a problem. Figure out some way around it that doesn't involve Google locking up the entire internet behind a UI element somewhere. Mobile phones is one thing -- my main browser is another.
I don't doubt there is a problem. I seriously question the ethics of actors that use the existence of a problem as a reason to exert further control over my e-commerce activities. If it looks wrong, even if most people probably don't care, it is wrong. This isn't hard stuff, guys.
I'm also already getting impatient with the seemingly endless parade of folks who are ready to play defense for Google. If Google thinks this is a good idea, let them defend it on their own.