10:45 AM Sunday Room: 8401
Web sites rely on various external resources, provided by 3rd parties: ads, beacons, widgets etc. But as more and more users start using ad-blockers and spam removers, you cannot rely on your site having undisturbed access to those resources anymore.
In fact, most software testing done today, does not take ad-blockers into consideration at all, leading to the dreaded, frustrating "bugs only happens on customer's machine" phenomena.
If you do not plan ahead, and anticipate the existence of such blocks, your application may misbehave, crash spectacularly, or react in unanticipated ways.
In this talk I will
1. Acquaint you with several common ad-blockers, and explain how they work
2. Demonstrate real live sites that misbehave when an ad-blocker is in play - to the point of service denial, and customer loss
3. Show web sites that deal with ad-blockers successfully and creatively
4. Finally, we'll get our hands dirty with some JavaScript code that would allow you to make your applications immune to ad-blockers effects, and ensure you will not lose potential customers due to unforeseen 3rd party resource behavior
At the end of this talk you'll be:
1. Aware of ad-blockers and their side effects
2. Be prepared to proactively include ad-blockers in your tests
3. Put into place code that degrades gracefully if an external resource is blocked.