Your script helped me find the issue in our logic.
It is fixed now.
From the 650 newest archived posts.
Likes as archived at fetch time, adjusted for how long each post had been up. Scored posts only; the full score pass runs after the import.
Your script helped me find the issue in our logic.
It is fixed now.
While we figure out what is wrong with the iPhone you can switch chat version from settings
Sorry for inconvenience.

Fixed, thank you
Chat should be fine too, thank you!
It was broken for quite a while. Thank you for reporting it!
How strange, for me it worked. But what I saw was something different.
What browser and OS is that?
Is it fixed now?
Thank you TNARGi, that's a good one.
Should be fixed now.
Oh, thank you. That came out after some accessibility fixes.
Resolved now.
That's fixed, thank you!
Your script helped me find the issue in our logic.
It is fixed now.
This is a specific behavior of the Samsung browser, and it’s a tricky one to handle.
It’s triggered when interactive elements are placed close together, the browser magnifies the area to ensure your tap lands on the right spot.
The interactive elements here are the bonus icons, the rounded boxes below and above the weapon image.
Probably, if we moved all these elements further apart, it would solve the issue, but this is not feasible at this point - we can't fit them all in the ui otherwise.
I think if you try tapping the middle of the weapon image, it will solve the problem.
Let me know if that helps.
Thank you for the report.
We recently made changes to prevent images from overflowing in the newspaper, which forced them to 100% of their parent’s width. That introduced an issue in cases where images are wrapped in an < a > tag.
I’ve adjusted the styling so image sizing is based on the main editor content container, not intermediate parents. This should resolve the problem.
That's fixed. Thank you!
It looks like the problem was just that the cursor wasn't in the editor.
I fixed it by adding some logic to ensure the cursor stays at the end of the text.
I wasn't able to reproduce the issue, so I've implemented a 'blind fix'. Please let me know if this still occurs.
I searched TinyMCE's GitHub issue tracker and couldn't find similar requests - this appears to be a very niche use case. TinyMCE also doesn't expose an API for merging adjacent tables, so it would be fully custom work on our side.
Auto-merging tables when there's no
between them risks breaking cases where someone intentionally has two separate tables next to each other (e.g. different column counts or different data sets). It's not a safe general rule.
For now the workaround remains using source edit mode to merge the table tags manually.
Table editing on mobile is generally a pretty rough UX, so I don’t think this is something we can “fix” on our side.
Since we’re using TinyMCE under the hood, we’ll get whatever level of mobile support they provide, but we’re not planning to build custom mobile table-editing behavior on top of it.
Thank you for the info about reproducing the bug.
I'll ask QA to help me with that.
Regarding the backup, since it is not present in our latest backup, retrieving it will be more difficult. I'll pass the note further.
That was fixed.
Thank you!
I guess we fixed that and forgot to close it.
Thanks for reporting this!
The notes bug was fixed long ago. I didn't see any changes in your notes in the last days, except that another note was selcted and an empty note was deleted.
If you still have a bug, it would be nice to have exact steps to reproduce.
Thank you!
What exactly isn't working?
That was some weird cache issue that we were sure we had resolved.
Please provide a screenshot, the name of your browser, device and OS.
Thank you.