Fixed by revision 102949.
The correction will be available in the next 19.05 release (and sooner in the 19.03 beta release).