Steffen has pounced on that bug and lists it as "Resolved"... in v19.5
There is no timeline for a release of v19.5, it is still in alpha, so for now the work-around will need to work.
I tested back to v15, the problem seems to be new in v19.
Thanks for spotting that problem!