Hey curiosityGuy,
This is a known bug that is on Mozilla’s side of things and will require them to push a fix through.