Has SDMB always worked this way w.r.t. urls in posts?

And in Post #2, if I click on the little arrow to the right of the word Frylock, it goes here:

http://boards.straightdope.com/sdmb/showthread.php?p=18723167#post18723167

So, if I click on the text of the quote in Post #2, it can go to any of three different places, depending on where I click. But all of the text is clickable.

For me, post 2 works the same way it does for Alley Dweller: the link inside the quote box goes to Bo’s post, the chevron to Frylocks op, and anywhere else in the box to Frylock’s op as a separate page.

Chrome.

Okay, I’m going to guess here that the problem is having a link within a link, which (I think) is not allowed in HTML, but probably every different version of every different browser deals differently with it.

Correct, noparse is a vB code that tells vB to ignore the contained tags. It does nothing to other features of whatever browser and platform one is using.

Curiously, you ask what browser we are using, but never tell us which browser and platform you are using.

FYI, I’m posting this on my laptop running Windows Vista and Chrome, but I did look at the thread on my Android using Tapatalk.

My laptop functions as the others describe, the quote boxes are solid links with nested links running to their independent sites.

Tapatalk works differently. It doesn’t recognize the noparse tags, so my first statement “quote from site” is an active link with no URL tags visible. Both statements “test link” are quote boxes that are not links. Clicking anywhere on the post that is not an active link highlights the post for inclusion in a reply, as it typical for Tapatalk.

Actually Digital is the new Analog was right: noparse does work with bare links, but Viglink makes them back into links anyway.

Also, apparently trying to quote something with [noparse] in the middle of it breaks the quotes. :slight_smile:

Ah, that noparse opened a tag and it didn’t close. DOH!

If you put [noparse] tags around the [noparse], it noparses the noparse!

I had layers upon layers in post #8 :slight_smile:
It’s difficult to explain noparse without using it liberally. I spent a while with different formats to make sure everything was done right.

ETA: Example of what **fachverwirrt ** is talking about. I could fix the coding, but then I’d be editing the text inside a quote box.