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 trial
kyle rees
1,480 Pointswhat does the w3c actually do
i know that w3c is responsible for setting the standards of html and css but what are they actually doing cause even thought there suposidly setting standards browsers seem to have free rein on how they do stuff
if the fact that they all render the same tag a little bit differently wasnt enough some seem to go as far as rewriting the standard altogether
take border radius the standard says border-radius: value now some browsers render this a bit differently which is part of my question but then others go so far as rewiring the standard to instead be
moz-kit-border-radius: value
some allow for short tags like #444 instead of #444444 some do just practically dumb things
i can understand things like margin and default padding cause there not in the standard so ofcourse thats up for interpretation as they designer sees fit
but what is it that w3c are actually doing if there not making a standard that is being adhered to i mean cant they just release a set of standardized models that help make the web a more uniform place so say they do this
this is the border radius it is coded like this border-radius when rendered it should behave THIS way wad no other way
and a side topic why cant ie just step out the game they have there own entire way of doing things and it is a pain in my butt (can i say $$$ here?) trying to make my stuff compatible with there way of doing things i mean sure they need to have a web browser to ship with there product and there giving it the college try but why oh why doe they have to put a half butt job into it im sure google or safari would be happy to ship there browser with windows and might even fork some cash ms's way
6 Answers
kyle rees
1,480 Pointsalso why is moz-kit even a thing its there code why not just have the standard border radius initiate the moz kit framework rather than making new code granted some of moz kit and googles stuff dosent fit within the standard liek chromes web apps but still keep the w3c stuff standadized if your going to start adding code atleast do us all a favour and add the features we have been screaming out for that w3c hasnt yet implimented or nether will
Matt Campbell
9,767 PointsWhy don't you send the W3C an email and ask them?
James Barnett
39,199 PointsThere are some W3C peeps on twitter, why not message them and see what they say.
Véronique Bellamy
20,810 PointsSeriously, Kyle. Chill.
Yes, the W3C sets standards but some web browser manufacturers deviate from that in different ways. There is a varying level of support for different features (i.e. HTML5 and CSS3 support in Google Chrome to standards abandonment in IE6).
It's our job as designers to design so that everyone can enjoy the design we are creating. If we cannot do this, we have failed.
So yes, it sucks that we have to be the ones who have to work at making sure that our design works and looks as well in Mozilla Firefox as it does in Google Chrome, as it does in Apple Safari, etc.
James Barnett
39,199 Pointskyle rees - It would seem that Paul Irish the man whose job it is to speak up for web developers at Chrome agrees with you that ...
Vendor Prefixes Are Not Developer-friendly
Here's his whole article on how Vendor Prefixes Are Not Developer-friendly
Other interesting article on the subject include blink is going prefix free also ppk's thoughts on Vendor prefix practicalities.
kyle rees
1,480 PointsJames Barnett - it wouldnt be so bad if theese prefixes were only on things outside of the standard like say chrome had a browser feature to allow you as the developer to idk rotate backgrounds without javascript or animate text something that was not even thought of by the w3c yet id understand that cause then its not in a standard but with border radius its just splitting hairs and actually verry childish its like devs this is border radius and the devs all goint "NO ima call it curvey borderness" but anyway ima check out those links you sent me