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

What's our progressive enhancement policy? #96

Closed
KimberlyMunoz opened this issue Nov 3, 2015 · 1 comment
Closed

What's our progressive enhancement policy? #96

KimberlyMunoz opened this issue Nov 3, 2015 · 1 comment

Comments

@KimberlyMunoz
Copy link
Contributor

Mike left an issue on Capital Framework about discussing our progressive enhancement policy. This is something I'd like to discuss here and eventually have a section on in our standards.

cfpb/capital-framework#12

We talk a lot about what browsers we support and what the experience should be like for them, but what should the experience be for older browsers. I think that for anything where the general public is our audience*, everything should work. By work, I mean forms should submit, pages should render, you should be able to read information and not have anything blocked by a bad layout that you can't remove without opening devtools.

I think there's probably more room for nuance, especially when it comes to what we decide to use polyfills for, what we use vendor prefixes for and what level of support we want to have for older browsers that don't necessarily do cosmetic things like border-radius correctly. I think we already have a solid unspoken standard on these things, but it'd be great to have them in guide.

@KimberlyMunoz
Copy link
Contributor Author

Moving discussion to #104

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant