> This is now fixed in 'next'.

Great; it works now. Thanks!

Reply via email to