Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Burying the URL

allenpike.com

Post reply on HN
Print view View original

331–340 of 376 posts

Re: Burying the URL

#331

Post by vitd »

ndomin wrote: post #328
mreiland wrote: post #310

Earlier quoted context omitted.

I already really dislike that win7 hides the filepath, and lies about it in many cases. It makes me click on the bar to actually see where I'm at in the filepath, please don't take that design mistake and apply it to the web.

I hope you've never used a mac in that case. Good luck finding a filepath with them. One of my biggest annoyances with mine right now.

You can choose "Show Path" from the "View" menu in the Finder. At least it isn't as hard to understand as "Enable origin chip in Omnibox".

Re: Burying the URL

#332

Post by busterarm »

ajanuary wrote: post #179
busterarm wrote: post #108

Earlier quoted context omitted.

Yeah but at least if you can get them to that bar or at least "Open Location" you can semi-predictably get them to a website where you can get the problem solved or narrowed down. Once you obscure URLs, web browsers become _impossible to support_. Of course Google doesn't care, because support isn't part of their lexicon.

You can still type URLs into the bar. It's easier to direct them to it because it always has the same prompt text. "Do you see a box that says 'Search Google or type URL?'? Great, type this into it..." The thing that's harder is getting them to read the url back to you.

That's my point. You can't get them to verify where they're at, because you tell them to go to X and they can't confirm they're at X.

Unsupportable.

Re: Burying the URL

#333

Post by LeoPanthera »

ndomin wrote: post #328
mreiland wrote: post #310

Earlier quoted context omitted.

I already really dislike that win7 hides the filepath, and lies about it in many cases. It makes me click on the bar to actually see where I'm at in the filepath, please don't take that design mistake and apply it to the web.

I hope you've never used a mac in that case. Good luck finding a filepath with them. One of my biggest annoyances with mine right now.

View > Show Path Bar (⌥⌘P)

Re: Burying the URL

#334

Post by harywilke »

ndomin wrote: post #328
mreiland wrote: post #310

Earlier quoted context omitted.

I already really dislike that win7 hides the filepath, and lies about it in many cases. It makes me click on the bar to actually see where I'm at in the filepath, please don't take that design mistake and apply it to the web.

I hope you've never used a mac in that case. Good luck finding a filepath with them. One of my biggest annoyances with mine right now.

right click on the title of a finder window.

Re: Burying the URL

#335

Post by Domenic_S »

ndomin wrote: post #328
mreiland wrote: post #310

Earlier quoted context omitted.

I already really dislike that win7 hides the filepath, and lies about it in many cases. It makes me click on the bar to actually see where I'm at in the filepath, please don't take that design mistake and apply it to the web.

I hope you've never used a mac in that case. Good luck finding a filepath with them. One of my biggest annoyances with mine right now.

Highlight a file in Finder, press command + i. Info pane shows path.

Or, drag a file from Finder to the terminal --> terminal prints the full path to the file.

Re: Burying the URL

#336

Post by Domenic_S »

mreiland wrote: post #310
albertsun wrote: post #307

Earlier quoted context omitted.

It might test well in metrics, but this is the kind of thing that points out why purely data based decision making can be dangerous. A-B testing assumes users will all behave the same in the future as in the past. But people's future behavior is dependent on their present behavior and experiences. With repeated exposure to URLs more people will learn how URLs work. Hiding URLs means that people will never be able to…

I already really dislike that win7 hides the filepath, and lies about it in many cases. It makes me click on the bar to actually see where I'm at in the filepath, please don't take that design mistake and apply it to the web.

I hate that copying the domain in a modern browser copies the protocol along with it. Highlight just "google.com", copy. Paste it and what is pasted? "http://google.com/". Makes dig/whois really annoying.

Re: Burying the URL

#337

Post by dublinben »

ndomin wrote: post #328
mreiland wrote: post #310

Earlier quoted context omitted.

I already really dislike that win7 hides the filepath, and lies about it in many cases. It makes me click on the bar to actually see where I'm at in the filepath, please don't take that design mistake and apply it to the web.

I hope you've never used a mac in that case. Good luck finding a filepath with them. One of my biggest annoyances with mine right now.

I think it's quite ironic that you just received four different suggestions of how to solve this problem. None of that would even be necessary if they didn't try to hide the information in the first place.

Re: Burying the URL

#338

Post by whatts »

The question remains whether we (or rather you, the Chrome team) should leave such a decision to some "metrics". What has happened to smart decisions, bold moves and instinct?

Re: Burying the URL

#339

Post by magicalist »

akerl_ wrote: post #223
antr wrote: post #176

Earlier quoted context omitted.

I'm going to be a cinic: if the Chrome team sees that users use Omnibox/Google more to got to the desired URL, that would be a positive thing (for them). Why type the URL when you can go via uncle Google?

Except given the recent trend, too many decisions like that would likely result in LibreAlloy or something similar. They have a lot more breathing room to behave that way with gmail and Youtube and similar, where the value they are providing is in serving the content, as opposed to Chrome where the code is more or less available and their value is in developing the open source environment. Clarification: I'm not sold…

It would actually be much easier than with most products, since this is just a change in the UI. You could fork Chromium while still keeping Blink upstream, and build whatever UI you want (somewhat similar to what Opera is doing).

Re: Burying the URL

#340

Post by altcognito »

jasonlotito wrote: post #253
RegW wrote: post #224

Earlier quoted context omitted.

Hmm, so I guess their stats are likely to be skewed. Being based on the choices of those that don't know or care how the web works.

This is only in Canary, so these are choices being made by people who are opting in to using that version. It will be skewed toward early adopters. If you are using Canary and NOT reporting back, you don't know how Canary works and shouldn't be using it.

Should we use the "report an issue" option in Canary, or file it under:

https://code.google.com/p/chromium/issues/detail?id=368725&q...

?

Post reply on HN