I was just affected by this starting with an upgrade to 131.This is either on purpose or Mozilla has no clue why it is happening or whats causing it, or at least they aren't telling us. I have found nothing official anywhere-just what some people are...