Search results for:

Looking at that page - probably best leave them out.

Imagine what this place would look like.

I never built them in.

Not hard to do so though.

I see that someone has done the hard bit of making a list: https://github.com/markdown-templates/markdown-emojis

Do markdown emojis work? Or are they not supposed to?

:smile:
:+1:

It's super rare as an edge case, but as the first post could be deleted the thread and the post are different things in the database... Created in two database calls. So there is the rare possibility of the second call failing or a timing issue resulting in the thread being in the cache before the first post is in the cache.

I clicked into this thread just now, and it was completely blank (0 posts).

I posted out of curiosity and was then the only post in the thread. On refresh the original OP appeared - as post #2.
Not an issue I need fixing, but wondered how it could occur, surely a thread is created once it’s first ‘reply’ is posted?

Any way around this?

If you scroll up so the comment toolbar is at the top of the screen, the formatting pop up will be underneath the text. Edit: What @Velocio said...

Drag doesn't work for me on stock Android

have you tried dragging the popup box?

Works on my Samsung tablet but not on my Sony phone. Since the former is at least two generation of Android ahead, it might be an OS feature

Perhaps this is a custom thing on my phone, but have you tried dragging the popup box?

Nice tip, cheers!

I add newlines at the top to move the text down. The forum gets rid of them when you post.

Any way around this?

A few.

1. Scroll the content so the overlay goes under the text.
   
2. Just use markdown... I.e. **bold** yields bold.
   
   

I do the latter. I just use markdown in my messages.

Selecting text in a comment you're writing - the options often block the formatting options at the top of the text box. Any way around this?

Just checked on another forum and it does the same. Must be a Chrome bug.

The text field here is just a textarea, a primitive HTML form field.

There's really nothing special going on and the code here hasn't changed in years. I'm curious why it's happening, but I don't think it's this site doing it.

It only happens on the lfgss though, actually it only happens in the comment editor. Can't say I've compared to another text entry field. Doesn't really bother me, just seems odd.

Nothing to do with this site... You've installed something or configured something on your phone.

Strange thing on Android/Chrome mobile: when selecting text I only get bing search as an option. Usually I get web (Google) search and bing.

Ah right, best of luck with that, sounds like a chore.

Similar effort.

The backend is well maintained.

The frontend is abandoned but I have a project to rewrite it without Django + Python + Bootstrap... just a Go server with Go templating, and cleaner CSS.

How much work would be involved in a dark mode theme? Similar level in terms of setting up a build environment or whatever? Used to mess around a lot with userstyles and the Stylish plugin but that was just a layer on top of everything.

No worries.

And yeah, that's why I haven't fixed it either.

Similar to a few other small quirks I know about which 6 years ago made sense and were the right amount of effort. But now the browsers are doing things better and there are better Go libraries for me to do things.

In time I'll get around to these... but I'm not really putting in the evening and weekend work I should to make that soon.

Well, I won't be doing that, but thank you for the detailed explanation of the obstacles involved. Hope you have a good evening.

Fair enough, and I accept PRs.

The code in question is here: https://github.com/microcosm-cc/microcosm/blob/master/models/markdown.go#L193

It's a simple regex text replace on textual data within HTML. It is a fast, forward-only parser that is provided by the core Go team and this does not have context of the parent node merely the current node and type.

To fully achieve what you need we'd probably need a full DOM tree here to ensure we don't perform the replace text where an ancestor is a code or preformatted element.

Once done, you'd need to also ensure the CSS works cross-browser to ensure that the layout isn't broken for all comments... only for the comment that exceeds the standard width (as it won't now wrap). This is harder, as the version of Bootstrap is 6 years old, and the version of Django is 6 years old, and neither build any more. So you'd need to start by resolving all dependencies needed by Django and node so that you could build both again... then you could make the adjustments to Bootstrap and push them into the Django build which I could merge, build and then ship.

PRs happily accepted.

Or it's good enough as what you describe is an edge-case we can live with.

I understand your point, but given that code blocks are specifically used for situations where every character matters, introducing new ones seems like a bad behaviour.

Context: https://www.lfgss.com/comments/16327731/

Fwiw the code block text reflows fine on my phone at a different point in the string. Your example string of numbers weirdly doesn't, it's one character too wide for the screen.