your post content, NEW POST CONTENT
As Michael explained, it actually seems that the bug is on the Mozilla side rather than Discourse, so there’s not much we can do from our end.
I’ve asked our dev managers to assess how we can proceed in this situation and if we can assign one of our engineers to dig deeper. If it’s confirmed that the bug is on Mozilla’s side, even if we were to open a bug report with them, we would have to wait for their timelines for a potential fix, which will depend on the priority level assigned by them. The timelines won’t be short, or at least that’s usually the case.