| What | Removed | Added |
|---|---|---|
| Resolution | --- | WORKSFORME |
| Status | NEW | RESOLVED |
Hadn't noticed this was already brought up and fixed in a branch. Sorry fo the noise. With brief local testing it looks fixed by b7ae412c6f7050b917d8b0bf2dadb212d740d8a5 which is already in mainline