Earlier quoted context omitted.
The full url with http:// is added to the clipboard when you copy.
Which "breaks" WYSIWYG.
So? Do you think people will be upset if they copy and paste a link and it has http:// put at the start?
Google Removes http:// from Chrome
11–20 of 74 posts
Re: Google Removes http:// from Chrome
#12What happens on Copy/Paste? google.com http://google.com are not the same in the context of the web.
The full url with http:// is added to the clipboard when you copy.
Only if you copy the entire link. If you try and extract a subsection like a directory, by either dragging across, or by shift unselect, it will not copy the 'http://.
A fringe case? Maybe, but I've already run into this pain a few times jumping back and forth from chrome to emacs.
Re: Google Removes http:// from Chrome
#13Re: Google Removes http:// from Chrome
#14Good move, but they need a new way of showing https or a broken https site.
Re: Google Removes http:// from Chrome
#15Earlier quoted context omitted.
Which "breaks" WYSIWYG.
So? Do you think people will be upset if they copy and paste a link and it has http:// put at the start?
"upset" is not the consideration. There is potential for functional confusion, with a basic function, where none existed before.
Re: Google Removes http:// from Chrome
#16Just noticed this on my daily build. I actually kind of like it. Copy/paste works just fine on Ubuntu Karmic.
Re: Google Removes http:// from Chrome
#17Monopoly
Re: Google Removes http:// from Chrome
#18The author had to pick on Apple..
Re: Google Removes http:// from Chrome
#19Since the OS X pasteboard is clever enough to add http:// back in when copying the url from the location bar, this actually works pretty well on my Mac. I like it too. I can see how it'd be intensely frustrating if the pasteboard doesn't work, though.
The addition of 'http:// is made by Chrome itself, not OSX.
Re: Google Removes http:// from Chrome
#20Earlier quoted context omitted.
So? Do you think people will be upset if they copy and paste a link and it has http:// put at the start?
"upset" is not the consideration. There is potential for functional confusion, with a basic function, where none existed before.
"...where none existed before."
For you maybe, but part of the reason they're removing it is because many average users had no idea what it was for.