Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialBridget Word
3,237 PointsBrowser support?
What is browser support? Also what is the site "can I use.com" for?
3 Answers
Ben Reynolds
35,170 PointsWhen the developers who maintain web technologies such as javascript, css, etc add new features, the next step is for browser developers to update their browsers to understand those new language features. Since every browser is maintained by a different organization, some browsers will be updated before others. Even browsers from the same developer but for different platforms might have differences, such as Firefox desktop vs mobile.
This is why you sometimes need to add multiple css rules for the same thing (one version for webkit, once for mozilla, etc) but it's not limited to just css. One thing you'll pick up on quick as you test code is how stubborn some browsers can be, particularly internet explorer and edge. I still have an old HTML5 book with a whole section called "Dealing with Internet Explorer."
That's why caniuse was made. It lets you look up a feature and see which browsers (and which versions of them) support it before you spend a bunch of time writing code that doesn't work.
Kieran Barker
15,028 PointsHey Bridget, not all browsers support all features. Can I Use is a website that shows you which features are supported by which browsers :)
Bridget Word
3,237 PointsSo how would I know which browser to write code for? I hope that makes sense.
Ben Reynolds
35,170 PointsThere are a lot of them out there today, but realistically you should at least shoot for Chrome, Safari, Firefox and Edge at a minimum (don't forget to test your site on mobile too). Thankfully this doesn't mean you're going to have to write everything over and over. Most of the common css rules you'll write are pretty consistent across browsers and don't need any trickery, and there are tools to help when they do.
Normalizers, frameworks, preprocessors, all of that stuff is built around getting people closer to a code-once-deploy-anywhere workflow. None of them are perfect but they do make things a lot easier.
I wouldn't stress about that yet though. It looks like you're doing the intro to css course. At this stage, focus on writing good clean plain vanilla css. If you get really comfortable with that, learning that other stuff when you get to it will be pretty straightforward.
In the meantime, I'd recommend going to your favorite site, hit that F12 key and start messing with the css and see what it does. Better yet, pull up the same page side by side different browsers and see if you can spot differences. Since you're essentially just looking at a snapshot of the page when it loads (mostly) you can preview any css changes you want with the dev tools and just refresh the page to reset it.
Kieran Barker
15,028 PointsKieran Barker
15,028 Points'Dealing with Internet Explorer', hahaha. I love it.