In Special:Translate, insertables hide text in longer messages.
I can see on both translatewiki and Meta. Screenshot:
Update: I can reproduce it in Firefox 87 (Nightly), but it works correctly in Chrome 88. So maybe it's a Firefox issue.
Amire80 | |
Feb 6 2021, 8:18 PM |
F34408517: image.png | |
Apr 20 2021, 1:29 PM |
F34276535: image.png | |
Apr 7 2021, 5:16 PM |
F34256626: fx88-padding-ignored.png | |
Apr 6 2021, 11:32 PM |
F34095226: Screenshot_2021-02-08 Translate - Meta(1).png | |
Feb 8 2021, 3:11 PM |
F34093798: Screenshot_2021-02-06 Translate - Meta.png | |
Feb 6 2021, 8:18 PM |
In Special:Translate, insertables hide text in longer messages.
I can see on both translatewiki and Meta. Screenshot:
Update: I can reproduce it in Firefox 87 (Nightly), but it works correctly in Chrome 88. So maybe it's a Firefox issue.
I tested it with Firefox 78.7.0esr, but I can’t reproduce it with 86.0b6 (Developer Edition) either. (Both have English (US) locale.)
The message seen on the screenshots of both of us is m:Translations:Tech/News/2021/06/47/he.
I think adding a blank line at the end should work this bug around. When saving the Translations-namespace page, this blank line is dropped, and I hope it’s dropped in the actual translatable page as well. However, I couldn’t test this, because…
I think I’ve tried it, but searching in Bugzilla is a nightmare for me. I found nothing either because there is really no such bug, or because I just failed to find it. Anyways, it seems to work again in 89.0b1 (Developer Edition), so if everything goes well, it should land in stable Firefox on June 1. If adding blank lines doesn’t work for some reason, you can download Beta or Developer Edition for the time being.
Firefox v78 (affected) is an ESR version. The next ESR version is v91 to be released end of July 2021, to supersede v78.
No, Firefox 78 is unaffected, affected ones seem to be only 87 and 88. Fortunately neither of these is ESR, so stable release users who have installed the now 11-day-old v89 are no longer affected, while ESR users weren’t and won’t be affected at all.
Ah thanks, I misinterpreted T274040#6811452. In that case I'd say let's decline this task?
Or close with any other status. It’s not exactly declined, since there was a valid issue, which has been fixed, just not by us and without us reporting it.