this is now fixed with FF v75 nightly - thanks @ecbos_ for the quick turn around, and thanks @ivarPrudnikov for the bug report