fix: prevent browser translation DOM crashes

[sleroq]

Resolves #323

Chrome translation replaces text nodes that React still expects to find.

Changes:

• post content: reuse elements instead of rebuilding them during updates.
• sign-in buttons: put each label inside a span so React can safely replace it with a loading spinner
• timestamps: wrap in span, making updates safer after translation

To be clear - the crash I've reproduced was only caused by the post content. Other stuff in theory can cause a crash as well, but it's not super necessary.

[y9san9]

Sorry, I missed all the PRs. Can you please delete merge commit and rebase instead?

[y9san9]

Honestly I don't think it should be a context. It's makes things more complicated than it needs to be

[sleroq]

Context helps there because this way we avoid remounting potentially translated markdown content. But this may be unnecessary change I made while searching for the cause of the crash.

I'll look into it later and try to simplify this pr

[y9san9]

To be clear - the crash I've reproduced was only caused by the post content. Other stuff in theory can cause a crash as well, but it's not super necessary

Can you point what was the reason of the crash specifically?

[sleroq]

@y9san9 Translate plugin is replacing the text nodes with the translated ones, react then is failing to edit removed node or insert elements in relation to them. Wrapping text with span fixes this.

Alternatively we could just instruct translate extension not to translate the site, but probably some other extensions would do the same so I think this is worth it.

[y9san9]

@sleroq Yeah and can you point to the specific lines in this PR that wrap text into spans in the post description?

I am from mobile now, I hope you are not :D

Also would be nice to separate this single thing and other changes, since I am not against optimizing for translaters