Yep! @mblaney is correct.
At first I thought this was conflicting with another component on here, but since reaching out on Meta it’s been confirmed this is a safari problem specifically 
3 Likes
Yep! @mblaney is correct.
At first I thought this was conflicting with another component on here, but since reaching out on Meta it’s been confirmed this is a safari problem specifically