This issue is fixed now also in stable version 1.2.2.
The release candidate contains additional revisions, so the next one will likely be version 1.3.3-RC.5+modifiers due to the patch level increase. Unless I find time to do a stable release directly.