5 ms·
It says that firefox and webkit browsers fail on border-radius, that's only because they use -webkit-border-radius and -mozilla-border-radius and Microsoft only
by papachito 16y ago
It says that firefox and webkit browsers fail on border-radius, that's only because they use -webkit-border-radius and -mozilla-border-radius and Microsoft only tested border-radius which is the one supported by IE, not very honnest especially knowing that gecko and webkit had those for years before IE.
- jasonlotito 16y agoBut, to be fair, do they support border-radius? I understand what you are saying, don't get me wrong. But either a standard is supported or it's not. If you want to get technical: Firefox, Safari, and Chrome have 0 support for the HTML5 standard, considering HTML5 isn't official yet. But they still work toward meeting proposed standard. Competition is good. If IE9 supports border-radius, and that pushes FF and others to support border-radius without the vendor tag, might that be a good thing?
- darrenkopp 16y agovendor tags are a plague. if it's not in the spec, fine, add them, make your browser appear pretty, but when it hits the spec, you need to pull support for your specific one, or make damn sure you support both.
- nex3 16y agoborder-radius isn't in the spec. The CSS3 Backgrounds and Borders model isn't final yet: it's just a candidate recommendation. See http://www.w3.org/Style/CSS/current-work http://www.w3.org/Style/CSS/current-work
- studer 16y agoThe whole point of promoting something to candidate status is to get people to start working on implementations. http://www.w3.org/Consortium/Process/Process-19991111/tr.html#RecsCR http://www.w3.org/Consortium/Process/Process-19991111/tr.htm... "A Candidate Recommendation has received significant review from its immediate technical community (resulting from the Last Call). Advancement of a document to Candidate Recommendation is an explicit call to those outside of the related Working Groups or the W3C itself for implementation and technical feedback."
- geocar 16y ago> ... and that pushes FF and others to support border-radius without the vendor tag, might that be a good thing? Only if border-radius doesn't change it's semantics; say the standard switches from radii to area. Or perhaps they add some semantics for negative lengths. If anything like that happens, then we now have two border-radiuses: Microsoft's and everyone-elses. I think that with border-radii this isn't likely, but for whatever is still under debate, we could still be looking at this sort of thing.
- jasonlotito 16y agoI know. But then you have people saying that X-browser has HTML5 support, but HTML5 isn't even finalized. This means all those sites supporting HTML5 aren't supporting a finalized standard. So you can't use HTML5 now... technically. If you do, you aren't following the standards. Canvas shouldn't be used, nor should the video tags, for anyone who cares about standards. Technically. Getting a little to anal? =) Okay, before someone jumps on me and thinks I'm being serious, yes, I agree with you. It's 'dangerous,' but at some point, someone needs to say "Damnit! Let's make this work!" After all, you don't see anyone saying we should use vendor tags for HTML5 markup, even though HTML5 isn't complete, and can, and still does, change. The great thing about standards is that there are so many to choose from. - Someone else, some other time.
- iaskwhy 16y agoActually, for the extreme (but sometimes useful) cases, IE9 really shows why the other browsers fail at border-radius: http://blogs.msdn.com/ie/archive/2010/03/19/the-css-corner-about-css-corners.aspx http://blogs.msdn.com/ie/archive/2010/03/19/the-css-corner-a...