Hm. I may very well be the only one who thinks the behavior is unintuitive then. It seems to me though that NodeBB could show "[click to preview]" from the start as it can generate that information immediately then can cache the full preview in the background.
The problem is that there's no way to tell whether iFramely will handle a given URL or not before you've gone and called it anyways.
I suppose though that instead of immediately showing the result, once iFramely does catch in it should first show the "Hey this is an embed, click to enable preview" and not initially render it...
Better Mortgage NMLS #330511. Better is a direct lender dedicated to providing a fast, transparent, and online mortgage experience backed by superior customer support. Not available in all states. See better.com/about-us/licensing-disclosure.
I dunno, it seems to work okay.
It can parse better now that I updated the plugin a minute ago.
@tsaukpaetra meh, i've had the title show me plenty of randomly wrong shit. it's pretty much useless for telling what topic/thread you're reading.
he's just on the thread list... i've gone into different threads altogether and had some other thread's title stuck up there.
@ben_lubar I understood what you meant, though. The composer preview (and the expanded reply section under posts, too) is significantly special enough that CSS that's supposed to style posts (and does style them once they're posted) sometimes doesn't apply to them there, and has to be fixed.
(I mainly just noticed that in my userscript development.)
@boomzilla It because if you try doing the pure CSS way you can't control the height and the play button is based on the videos height. I know what you are trying to do, I tried doing it before. But there is a lot of style tags that are set by JS.
If you could embed youtube cleanly, you could use a height of element ::after to make sure that the width / height was correct with the height (aka correct aspect ratio).
Something like that. You need to view in js fiddle otherwise it won't make sense because nodebb previews it badly.
@3rd-Party-Developers @administrators Working Text2Speech working module available here https://github.com/hariom282538/nodebb-plugin-text2speech #Text2Speech Note: Tested env Lavender(theme) & NodeBB v1.5.1. -> Original Plugin has some issues and didn't...
opens browser console
ssu = new SpeechSynthesisUtterance()
ssu.text = 'hello world'
well then. i am totally going to be abusing that API in the near future.
That's how I got banned from a Discord server once.