Posting a link - broken

for over a couple of months now, I have been not able to use the “post a link” button in the little toolbar above the message edit window.

I did some testing, and it is crashing when I press the button. I am able to cut and paste a url directly into the message window.

I know others have this same problem, so I am going to assume it’s not me. Hopefully, someone is working on a fix for this.

In the meantime, can someone post the syntax created for a link, so I can insert a link and give it a title? I remembered the /url tag, which allows me to insert a link, however it leaves a thread looking messy. I’d like to be able to insert a descriptive title when it makes sense.

Right now, I have link, which works ok, but I can’t recall the format to shove the text in there, so when people read the post, they can click on a word/phrase instead of seeing the entire url.

Thanks!

Yahoo - Here’s a sample link. Just quote this post to see the exact text.

Or just look here:

[Yahoo](http://www.yahoo.com)

I’ve never had a problem with Post a Link button. What browser/OS combination are you using? What is crashing? The browser I assume.

There’s a known issue with the Safari browser where it exhibits exactly this problem (crashes when you press the post a link button). I don’t use Safari so I don’t know if anyone has managed to come up with a fix or workaround for it.

Some people have reported Chrome freezing.

I’m not aware of any problems with the post a link button using other browsers.

After poking around a bit, it seems that this is a bug that was introduced in iOS 8.3. Previous versions of iOS don’t exhibit this bug.

The latest info I could find was that the bug was still present in iOS 8.4 beta 1 (they are up to beta 4 now, no idea if it’s been fixed yet or not). Hopefully a fix will be in the final release of 8.4 which is due out at the end of June, I believe.

Well whaddaya know? There’s a “post a link” button in the toolbar!

Never noticed that before.

Happens to me with Safari on my iPad. I thought I had a workaround by using my backup browser, Chrome. Same result; safari crashes, chrome freezes.

ETA: Thanks for the info, engineer comp geek!

This is what I was looking for. I couldn’t remember the placement of the word before the end /url tag. Thank you.

engineer_comp_geek, thanks for spending the time searching for the actual cause. I have had some seriously strange behavior on my iPad since that update, and the Safari browser is virtually useless now. It hangs almost every time I try to load a page, and forget about clicking a link from a page that has miraculously loaded. That is an instant hang.

Clicking the “post a link” button makes both my Safari and Chrome browsers crash.

I hope whoever introduced that bad code is getting his walking papers. He/she has “caused me great annoyance and displeasure.” (John Wayne, Big Jake). But beyond that, I have tossed the Safari browser away, and will not even try to use it until I get word that the bugs have been fixed. It seems that Apple, MS, AND google all want you to use their browser, so Apple has lost me for a long time, and I suspect they’ve lost a number of others, too.

Chrome recently introduced a bug that affects many applications. Firefox has done so in the past. Browsers are complex systems that have to interact with all sorts of add ons, plug-ins, and poorly coded websites. Not excusing the bug, but it’s not clear yet what caused it or if the problem was actually introduced in the browser, a library, the OS, or somewhere else.

Not that the bug isn’t bad and RCA should be done to find how it escaped and address it. But my guess is that there’s no single person who caused it.

I would like to revise my call for the programmer’s head.

I’d settle for the person on the testing team that missed it.

If Apple is an ISO-certified shop (and I am sure they are), they have a testing group that should catch these types of bugs.

I know the stress involved in software releases, and schedules that must be met. Programmers can and do make mistakes all the time. That is just part of the software development process, so crucifying a programmer isn’t the way to go here.

Let’s get the tester!