Josh F. so are you saying you are not happy with having to do a CSS override and you were trying to do it natively within the Designer or? I was thinking it might have had something to do with some of the inherit CSS that we had in our global styles but I'm not seeing that CSS in your global styles right now.
yeah there is literally CSS being injected into the DOM - I can't figure out why though - I see you are using the Finsweet style guide and not ours which is generally fine so it rules out a corrupted backup on the style guide file itself.
At any point in this project did you have to revert to a backup or?
I'm sure Slater might have some idea potentially of what may cause a rogue style like this.
I also wonder if when we were creating this component, if we had CMS connected, which would allow us to style the alternate, and then we disconnected it but the CSS stayed? That would be wild.
