|
Thanks for the report.
cheers
Chris Maunder
|
|
|
|
|
|
It is a very old/known "behavior"....
Workaround:
1.) Before you paste the link press at least two time <enter>
2.) Now one time <cursor up="">
3.) And now <ctrl&v>
Doing it like this one should be out of Problems 
I'm considering publishing this as a tip / trick. But it's copied from ... I do not remember anymore 
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
I have never seen this problem, and I past links to messages most days.
|
|
|
|
|
Try the following:
1.) Make sure you have a link in clipboard
2.) Reply e.g. to this message
3.) Enter a text e.g. "test" in the first line
4.) Press <enter>
5.) Paste with Ctrl&V
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
|
Looks fine. Then most probably a IE (IE11 at the moment) issue. I know I should replace it but I'm so lazy 
Will try it now with chrome
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
|
Which browser?
cheers
Chris Maunder
|
|
|
|
|
Seems to be an IE (IE11 at the moment) issue. Chrome does not Show this behaviour (but IE showed it since several years).
It does not solve my Problem, but it answers my question
modified 19-Jan-21 21:04pm.
|
|
|
|
|
I see it in IE11. I work around the problem by hitting the spacebar twice before pasting. That seems to fix it.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Ain't it weird how this is browser-specific?
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
John Simmons / outlaw programmer wrote: Ain't it weird how this is browser-specific?
Well it's client side script, so it's not that surprising. I am just surprised it's IE that has the issue since that's possibly the most popular browser used by people who visit this site.
|
|
|
|
|
I only use IE11 from work because that's all they allow to be installed. At home, I use Firefox.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Nish Nishant wrote: since that's possibly the most popular browser used by people who visit this site
No - not even close.
IE use is about 5%. In comparison Safari is 3.5%, Edge is 3.3%.
Chrome is 73%.
cheers
Chris Maunder
|
|
|
|
|
Wow, that is extremely surprising - I would never have guessed that!
|
|
|
|
|
The issue is IE specific, so no, not surprising at all.
I wish the broswer manufacturers would just settle on WebKit and collaborate on building a fast, solid, consistent rendering engine we all agree on.
Except that Google has already scuppered that with Blink[^].
cheers
Chris Maunder
|
|
|
|
|
Wikipedia wrote: Blink is a fork of the WebCore component of WebKit[6], which is originally a fork of the KHTML and KJS libraries from KDE
When you start to fork from the fork, it is already a lost battle.
I guess this is a generic problem : everybody wants a standard, but based on their own special needs. And once something is published, everybody finds it so bad that they use their own solution or "fork". 
I am still baffled at the guy who managed to introduce mini-usb as a standard for smartphones.
|
|
|
|
|
Nothing beats the awfulness of USB 3.0 Micro B. USB by committee.
cheers
Chris Maunder
|
|
|
|
|
Yeah, I get this at least once out of every 3-4 attempts.
|
|
|
|
|
Just a thought, but should it show the Soapbox? Some of the subject lines there can get a bit ... um ... inflammatory.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
The discussions, when you have the Following tab selected, show those forums and tags you are following. It is customized for YOU. If you wish to follow the Soapbox, that's OK, only you and the other maniacs who are also following, will see those messages.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
That's kind of the point: I'm not following the Soapbox:
I have the following tab showing:
And I still saw Soapbox topics in the Discussions list.
Since that's the default for new visitors, perhaps the Soapbox (and possibly Spam & Abuse) should be excluded unless specifically included?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I've just noticed that it may be because I'm following myself, for some strange reason... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
