Turns out I was loading Bulldog's CSS AFTER Ad Manager's CSS, causing Bulldog's CSS to trump Ad Manager's CSS.
Ad Manager uses the html element to set custom/invalid font family names so that it can communicate with JS and we can have responsive ads. Because I had Bulldog's CSS come second, it overrode Ad Manager.
Ran into a bug today, pointed out by Melissa, that ad weren't loading in Chrome.
After most of a day of debugging, I narrowed down the problem to this one line:
When I removed
html,
, the ads loaded!Turns out I was loading Bulldog's CSS AFTER Ad Manager's CSS, causing Bulldog's CSS to trump Ad Manager's CSS.
Ad Manager uses the
html
element to set custom/invalid font family names so that it can communicate with JS and we can have responsive ads. Because I had Bulldog's CSS come second, it overrode Ad Manager.Took most of my day to find a five character bug.
Fixing now.