On 8/20/19 8:48 AM, Mike Hommey wrote:
> This is presumably fixed in 68.0.2-3

ah, thanks! :)

Regards,
Daniel

Reply via email to