Major cross browser compatibility issues

noname000

I am having a lot of Cross Browser comparability issues, and I am very confused. Paddings and margins look very different between:

Chrome / Safari (on Mac)

Chrome / Safari (on Windows)

Here are some attached pictures. How do I fix this?  

See the images here:

https://imgur.com/a/E9d3Us2.

The issues can be found across https://cobury.com. Here is the really big one: https://cobury.com/careers/.

Pablo

Hello,

You have a massive amount of Custom CSS code applied and this can be the source of the problem.

Our theme looks almost the same on the browser, and if this kind of issues (paddings, margins) would appear, we would notice that a lot of time ago.

Test, that our pre-built websites looks almost the same on different browsers.

You have to be aware, that little bit differences can be noticed because of different core code of browsers and it will not be almost not possible to avoid.

https://en.wikipedia.org/wiki/Comparison_of_browser_engines_(CSS_support)

There are some CSS libraries(normalize.css) which solve (not in all cases, but usually all of them) that problem, but we are not able to help you including it into the wordpress because we do not help with customizing the theme/wordpress files.

Thanks

Learn more: Video Tutorials | How To | FAQ Vote on what comes next

noname000

But there seems to definitely be a bug, the error appears before I even added any code. If I make a column with a h1 and a h6 it looks completely different on safari / chrome. This is not normally the case. I paid for support.. Can you not try to help look what is causing the bug? 

noname000

Try to open https://cobury.com/careers/ in safari, it is completely buggy/different?.

This is how it looks on Chrome compared to Safari with absolutely no css or code. https://imgur.com/a/aTwRqUv.

The bug can also be seen here. I just made 2 columns in muffin builder and they look completely different on the two browsers. I added no css:

https://cobury.com/cases/. See here... https://imgur.com/a/B8pc5qP

Edit: I found a solution. It is a Clearfix bug.