I filed bug 2003395 as a platform-bug here. Aside from us fixing that bug... the cleanest fix here would be for the site to move the space characters outside of the `rb` tags, as in reference case 1b posted on that bug. In the absence of those fixes, the first part of comment 4 (adding an explicit zero-width space after each ruby tag) seems like a good solution. That might introduce linebreaks in spots where they aren't intended, but nonetheless it'll be better than the layout we're getting right now, I think.
Bug 2003019 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I filed bug 2003395 as a platform-bug here. Aside from us fixing that bug... the cleanest fix here would be for the site to move the space characters outside of the `rb` tags, as in reference case 1b posted on that bug. In the absence of those fixes, the first part of comment 4 (adding an explicit zero-width space after each ruby tag) seems like a good possible sitepatch that we could ship. That might introduce linebreaks in spots where they aren't intended, but nonetheless it'll be better than the layout we're getting right now, I think.
I filed bug 2003395 as a platform-bug here. Aside from us fixing that bug... the cleanest fix here would be for the site to move the space characters outside of the `rb` tags, as in reference case 1b posted on that bug. In the absence of those fixes, the first part of comment 4 (adding an explicit zero-width space after each ruby tag) seems like a good possible sitepatch that we could ship. That might introduce linebreaks in spots where they aren't intended (and where other browsers don't break), after ruby elements that *do not* contain a space character; but nonetheless, it'll be better than the layout we're getting right now, I think.