howeller

Has anyone built banners using fonts hosted at fonts.cdnfonts.com? I was wondering if this was legit. Thanks in advance.

I am getting this same error with the plugin file hosted next to (or even inside a <script>) the banner document. No idea what's triggering a CORS from a single file. There's no errors on my pen below when I reference a CDN, but the error occurs on my web server & locally. Are browsers getting stricter or is there something about using it locally I am missing? Pen

I was wondering if anyone's had any experience with building ADA compliant banners. We've been getting more requests from clients for this, but have not found much guidance on it (looking at you IAB). From what I understand using semantic HTML tags + the aria attribute works for the most part to make a banner readable for sighted and unsighted users, but I've no idea how to setup something built in Animate outside hiding duplicate content in hidden tags. Thanks in advance.

I've been using Gulp for some time to offload repetitive tasks that come with building banners and I love it. You can code witha CSS preprocessor, mix in image compression, sprite sheets, minify code, and so much more. Lately I've heavily relied on gulp-compile-handlebars for compiling templates into banners. Definitely worth looking into.

I just ran into this exact issue with both EBLoader.js and adkit.js. The listeners for EBG.EventName.EB_INITIALIZED nor the adkit.onready() never fires inside an iframe. Did any of you ever get to the bottom of this? So far I've only tried removing the iframe sandboxing restrictions, but it did not fix it.

That did the trick! Your update has IE only making 2 divs like all other browsers. Thank you for taking time out to look at this! Can't wait until we are able to drop IE support.

Hi Jack - thank you for taking time to look into this. I am only seeing this break into 4 lines in IE11. When I add in display:inline-block into the <sup> tag it then corrects itself in IE, but then splits into 4 lines on most every other browser. Here's the link I am debug pen I tested in IE11: https://cdpn.io/howeller/debug/qBZqOBE/DqADdgDqJKeA It appears to change each time I make an edit. I do not have a membership on my personal account. We do have one here at work which this project is for. I'll have to dig up the account it's registered under.

Hi Zach - I am totally fighting the non support front. Plan B is to find a fix. I just added a Pen to my issue above. I can see this in IE11 when I paste the debug view URL https://cdpn.io/howeller/debug/qBZqOBE/yYMyLJZoPVOk Is that adequate? Thanks for looking into this!

I am using Split Text (v.0.5.8) to create a simple line by line animation which works awesome. I've run into an IE11 issue when I use^{tags in the string they get broken out into their own div which is set to be a block element. So my initial div: <div id="txt">I can't wait <br>until we drop IE11<sup style='font-size:50%;'>®}!</div> <script> var t1 = new SplitText(document.getElementById("txt"), {type:"lines", linesClass: "line-span", reduceWhiteSpace:false}); </script> will print 2 divs in most browsers as expected. <div class="line-span" style="text-align: left; display: block; visibility: inherit; position: relative; opacity: 1;">I can't wait </div> <div class="line-span" style="text-align: left; display: block; visibility: inherit; position: relative; opacity: 1;">until we drop IE11®!</div> But in IE11 it buts the <sup> into extra an div and prints 4 divs. <div class="line-span" style="text-align: left; display: block; visibility: inherit; position: relative; opacity: 1;">I can't wait </div> <div class="line-span" style="text-align: left; display: block; visibility: inherit; position: relative; opacity: 1;">until we drop IE11</div> <div class="line-span" style="text-align: left; display: block; visibility: inherit; position: relative; opacity: 1;">®</div> <div class="line-span" style="text-align: left; display: block; visibility: inherit; position: relative; opacity: 1;">!</div> I saw Carl's video addressing the issue and tried the patch of adding display:inline-block; into the tag fixes the issue in IE11, but creates the same issue in every browser.