Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[V8 team proposal] Making sure that a new Chrome version does not break your website #7

mathiasbynens opened this issue Oct 6, 2017 · 4 comments


Copy link

@mathiasbynens mathiasbynens commented Oct 6, 2017

Session Title:
Making sure that a new Chrome version does not break your website

Session Abstract:

This session describes on how to test your web application in advance in order to find out if future Chrome releases might "break" your web application. The earlier you discover problems, the higher the chance for Chrome and/or you to fix them without impacting your revenue stream.

Approximate Duration:
15–30 minutes

Your Name:
V8 team

Your Twitter handle:

[x] No
[ ] Yes => Please share what do you need.

[ ] Advanced
[ ] Intermediate
[x] Beginner

Copy link

@mathiasbynens mathiasbynens commented Oct 11, 2017

Possibly in collab with @zoepage!

Copy link

@littledan littledan commented Oct 12, 2017

The group could also talk about what Chrome does to try to not break your web page, and how you can help Chrome to not break your page (not sure if this is interesting for people though).

Copy link

@natorion natorion commented Oct 12, 2017

@littledan that was the idea.

Copy link

@littledan littledan commented Oct 12, 2017

Oh I see, I misinterpreted it to be about how website owners can fix their site for new Chrome versions. Sounds great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants
You can’t perform that action at this time.