4 ms·
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 peopl
by zdw 13y ago
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.
- jaffathecake 13y agoView-source & devtools are also useful for people who know what they're looking at. Those things are not shown by default.
- justinschuh 13y agoChrome has been highlighting the origin component and de-emphasizing the path since its initial release, but the fact is that the vast majority of users are still very unclear about the security relevance of origin and easily fall victim to phishing attacks. So, the team that's working on this is intentionally investigating larger departures from the current URL display. Accepting that, what you see right now is an incomplete experiment, and no one involved would be happy with the result if it damaged the utility of URLs or made Chrome less useful for web developers.
- chr1 13y agochrome keeps both domain and subdomain black, which makes this kind of phishing easy. Firefox have a better approach of keeping black only the main part, and graying out everything else. Yet better solution would be to highlight domain with green color instead of https:// https://, and to scroll urls with very long subdomain to make domain viible. I rather liked how this[1] firefox addon added a bubble around domain, but kept url as selectable text. [1] https://addons.mozilla.org/en-US/firefox/addon/smart-text/ https://addons.mozilla.org/en-US/firefox/addon/smart-text/
- leoc 13y agoAn approach like greying out the path would be a good idea if it were in any way desirable for the path to be user-visible by default, but it isn't.
- Touche 13y ago> Chrome has bee highlighting the origin component and de-emphasizing the path since its initial release, but the fact is that the vast majority of users are still very unclear about the security relevance of origin and easily fall victim to phishing attacks. Barely. There's very little contrast between the two parts, not enough that you would notice that there is a difference unless you look very closely.
- gkya 13y agoEverybody is complaining about the lack of contrast between the root domain and the rest of the domain in the URL bar. I reckon, both in Chrome and in Firefox, there is quite noticeable contrast between the root domain and the path/subdomain. If the contrast was bigger, then the path would be unreadable, which undesirable too.
- Touche 13y agoIn Chrome the domain is black and the path is grey. You could make one red and the other green and that would be actual contrast. Or give the domain a background and border. There's more ways to contrast things than adjusting the lightness of black.
- gkya 13y agoMore contrast might be good, but I'd not take it in expense of ugliness.
- Touche 13y agoWhy does it need to be ugly? I'm not a designer, but I have a hard time believing that the only way to contrast two elements without making it ugly is by having them be a slightly different shade of the same color.
- gcr 13y agoDevs can just press ^L to select the URL, I think. That's what I do when I need to change/manipulate/view it anyway.