Great, it worked fine! Thank you for the quick fix ![]()
Have a great day!
Great, it worked fine! Thank you for the quick fix ![]()
Have a great day!
This is really a great component, but it currently still displays as a citation style in the revision history view. Can this scenario be supported? ![]()

It also appears like that in excerpts too, and in Oneboxes.
I suspect that it might be tricky to cover all the edge cases though.
Hi! I noticed a potential usability issue with the default Ctrl + Q shortcut on macOS.
Many Mac users instinctively press ⌘ + Q instead of Ctrl + Q, since ⌘ is the primary modifier key used for most shortcuts on macOS. Unfortunately, ⌘ + Q is also the system-wide shortcut for quitting the application/browser.
As a result, users may accidentally quit their browser while trying to insert a callout.
It’s not impossible, I gave it a try yesterday. I will see what I can do!
It should be hidden in excerpt unless something is broken again, but yes not hidden in onebox yet. I will keep in mind, thanks!
Good catch ![]()
Any suggestions? I’m thinking of using ctrl/⌘ + alt + c instead. That sounds safe, I hope.
I pushed an update.
Just a style issue: I’ve noticed that the code styling within quote callouts titles appears much shorter in length compared to normal text, which can cause it to be completely obscured by symbols like █ , and in languages such as Chinese, some larger text sizes may cause the four corners of its bounding box to go out of bounds, making it look odd.
I pushed a fix. It adds missing core CSS to <code> HTML in the callout title. Also, it removes extra newline spaces. Overall, this should be consistent now!
Absolutely love this, and have installed and activated it on my site, but can’t get it to work. I must be missing something but I can’t figure out what. Here’s my first attempt:
Thanks!
I can see it works on your forum, what was the issue? ![]()
Oh wait, it works? I left it non-working. I will look again after my meal! Strange…
OK this is really weird, it is in fact displaying correctly now both on mobile and on desktop. Some kind of caching issue maybe? Sorry for the bother – I didn’t do anything ![]()
Indeed, really weird. The only reason I can think is you had an error in the browser (javascript error) that prevents the rendering to happen, but the code in markdown preview and post is the same.
If you are able to reproduce on desktop again, it might be interesting to investigate. Look at the browser console (f12 or right click anywhere → inspect → console tab ) and look for errors.
When you told me it worked, I checked on my mobile and saw it had indeed. Then I searched for the page in Chrome on desktop, my secondary browser, and it wasn’t displaying. Went to Safari (fail), then came back to Chrome and probably reloaded and Lo and behold, there it was. Went back to Safari and… now working in Safari too.
Before posting I had of course reloaded multiple times, edited, re-edited… etc.
I’ll let you know when I try applying it all over the place if I bump into anything!