Re: Safari / Chrome / WebKit Issues
Mike. It was a CSS Positioning Issue, and Safari / Chrome are built on WebKit and behaved outside of a way that I expected. It was a float issue when using "none" as an option. Resolved by changing the float and how it was structured.
|