Earlier quoted context omitted.
Genuinely curious, what kind of metrics do you use to measure the effectiveness of a change like this?
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?
Burying the URL
231–240 of 376 posts
Re: Burying the URL
#232This is a new UI experiment that's deployed to a small fraction of users. We're looking at a few key metrics to see if this change is a net positive for Chrome users. (I imagine it may help defend against phishing). My personal opinion is that it's a very bad change and runs anti-thetical to Chrome's goals. I hope the data backs that up as well. But regardless, this change is far from shipping as the new default beha…
Re: Burying the URL
#233This is a new UI experiment that's deployed to a small fraction of users. We're looking at a few key metrics to see if this change is a net positive for Chrome users. (I imagine it may help defend against phishing). My personal opinion is that it's a very bad change and runs anti-thetical to Chrome's goals. I hope the data backs that up as well. But regardless, this change is far from shipping as the new default beha…
I can't imagine using a graphical browser without an address bar. Regarding the possible benefits, I think phishing would become a lot easier, if users don't see the URL any more, anyone can still link to phishing pages.
Re: Burying the URL
#234Earlier quoted context omitted.
stop using Chrome That may solve this particular problem, but then which browser do you use instead? Firefox has had its history of similar changes (although you can still use extensions), Opera post-12 lost a ton of customisability, and IE, although appearing to have the fewest irritating interface changes, also has the most rendering quirks. (Personally I'm less concerned with the rendering quirks than the UI chang…
I'm smelling a possible reboot of the browser paradigm. There are a few fundamental uses I see, and they're somewhat distinct: • Reading. For which stripping 99.99966% of Web formatting would be preferred. If I got content-heavy sites in a form similar to what Readability, Pocket, Instapaper, etc., delivers, I'd be much happier. Well, slightly less grumpy. I found it interesting that the Kobo tablet was, for a while,…
Want to read? I either fire up the Adobe PDF reader and load something from my history or I open my email/dropbox/trello card and tap an attachment, which opens up the PDF reader.
Almost all the interesting ideas in academia come in .pdf format, not .html. It just fits our use case better.
Want to shop? Fire up amazon i guess or fire up a web browser and go to amazon. Who cares if the "Amazon" uses standard HTML forms? The user doesn't.
Want to $x? Fire up $app_that_handles[$x].
Re: Burying the URL
#235This may be the reason I stop using Chrome even though I was a member of the team for 5 years. I NEED TO EDIT URLs. I need to copy and paste URLs. It was already annoying enough with it's removing of the protocol because sometimes I make a typo, try to edit it and it messes up and removes the protocol forcing me to edit it a 3rd time only after it goes as searches for something. Even as just a user I copy and paste U…
stop using Chrome That may solve this particular problem, but then which browser do you use instead? Firefox has had its history of similar changes (although you can still use extensions), Opera post-12 lost a ton of customisability, and IE, although appearing to have the fewest irritating interface changes, also has the most rendering quirks. (Personally I'm less concerned with the rendering quirks than the UI chang…
Re: Burying the URL
#236Earlier quoted context omitted.
> they're just acknowledging the fact that 99% of users don't need to see 99% of the URLs they visit on a daily basis. While we're talking about things we don't need, let's include this change . The fact is, for most of the last two decades we've already had a UI where users who don't care to attend to the URL don't have to, and users who care to notice can. What does this add? Nothing. But it does take away some leg…
> URLs aren't high tech any more than the address to your house is When you stop by the local coffee shop, do you take note of what its address is? The users have an idea what URLs are, they just don't care.
Re: Burying the URL
#237I dont see this as a benefit to users, most people I know dont even have a concept of what programming languages are. If I were to say Ruby they would be thinking of the gem.
Re: Burying the URL
#238hope safari, firefox won't go this road
On the concerning side, there's nothing Mozilla likes more than copying Chrome.
On the hopeful side though, they have remained strong in the face of combined search+URL fields, so this may be one place they continue to resist.
Re: Burying the URL
#239Earlier quoted context omitted.
Yes, it asks you when you first run it.
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.
Re: Burying the URL
#240I worry it will be the same as last time they removed the http from the url: Users: Okay, you removed the http from the url by default, but can I have an option to disable it? Chrome: No, just accept it https://code.google.com/p/chromium/issues/detail?id=41467