December 4-6, 2017
Vancouver, Canada

How to identify bad third-parties on your page

Being a developer of a third-party script means not only that you battle browser discrepancies and bugs, but also non-conforming code that exists on the page. We have spent countless hours debugging issues, only to learn that the culprit was an overwritten method or property that behaves differently than its original native. I will share with you the tools and methods we use to identify and workaround these party crashers.

View all 87 sessions

Charles Vazac

Akamai

I've been a web dev my entire professional career. I've written a charting package in VML (gasp!), single-page-applications before they were called SPAs, browser analytics code in vanilla javascript that "works" in IE6, SPAs transpiled from ES2017, and c++ for a popular web browser.

I love writing and reading javascript. I love figuring out how things work, why they don't, and how to make them better.

Read More

Comments

Please remain courteous and constructive. Comments will be moderated.

Vancouver 2017 sponsored by