Thank you, appreciated. It did used to work as I had wanted so I can only assume it has been via a change in Discourse at some point, there is probably a good reason behind it, but just in case there isn’t I thought I’d ask in the hope that I can revert to what I had
My apologies regarding the “F”, I will correct on our site also!
We have the same issue with any onebox in a quote.
Adding an internal Discourse link gives us the “inline” onebox: Oneboxes don't work inside quote blocks?
Twitter (or any other link) also doesn’t expand, we get “inline” too. x.com
It’s possible this broke as soon back when we added inline oneboxing, or a more recent regression, can’t say. Personally I’d call this a bug.
If you absolutely positively need to, this workaround can work, no guarantees it will work forever though.
<blockquote>
If you absolutely positively need to, this workaround can work, no guarantees it will work forever though.
https://twitter.com/triketora/status/986356346672082944
</blockquote>
Thanks everyone for looking at this and discussing it, truly appreciated.
It’s a shame it isn’t an intentional feature, as it has been very useful, not something worthy of consideration as a feature rather than a bug @codinghorror?
Thanks for the headsup about using the HTML markup @sam, I will give that a go for now and appreciate the warning that it may stop in the future.
If the site had already been oneboxed in a topic it seems noisy to have a huge onebox every time the link is mentioned again. Having it show as a link rather than a onebox in a quote seems preferable.
That is a very good point, I was obviously only thinking of the specific usage/need I had, which was to be able to display a before/after view of a users post.
I suspect it would be of little use to anyone else, so perhaps requesting its behaviour could be configurable, at a post level, wouldnt really be worth it.
I guess a better approach for myself would be to create a couple of screenshots instead and edit those where necessary.