Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.

Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.

How Chrome is trying to
improve predictability for developers How we work with other browsers to make this better How web developers can help improve the platform Image credits: https://www.ﬂickr.com/photos/toddle_email_newsletters/15575925446

Fight the platform less Reduce
the need for: Browser-speciﬁc code paths Workarounds for regressions Polyﬁlls for inconsistencies between APIs Shims that smooth over lacking interoperability

Break websites less Ship no
accidental regressions. Only deprecate features when we understand the cost and know it’s worth it. Be transparent about interventions, and give developers a smooth migration path. Image credits: https://www.ﬂickr.com/photos/dullhunk/4517822872/

Fail fast and obviously Decrease
the number of times a developer stares at a blank screen or searches aimlessly for help. Image credits: https://www.ﬂickr.com/photos/johnath/7356295658

The Web is a commons
It thrives on collaboration and competition Good communication between stakeholders is critical By Daniel Schwen (Own work) [CC BY-SA 4.0 (http://creativecommons.org/licenses/by-sa/4.0)], via Wikimedia Commons

Blink bugs! The best way
to discuss where chromium should improve for web developers https://www.ﬂickr.com/photos/brizzlebornandbred/12852086543

Take aways We’re trying to
treat the web as a single platform Test on beta and ﬁle bugs Star the bugs / features you care about Visit /feedback, try the Browser Bug Searcher Get involved - this is your web!