donum / curvycorners

Automatically exported from code.google.com/p/curvycorners
0 stars 0 forks source link

Must include -moz and -webkit tags #63

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
CurveCorners only works if both of:
-moz-border-radius
-webkit-border-radius
are included.

This seems silly, especially as Webkit now supports the official 'border-
radius' property. I reckon CurvyCorners should work if *any* of them are 
present.

What steps will reproduce the problem?

---
1. Download attached 'both-tags-proof.html'
2. Open in Internet Explorer
3. Open in Chrome, Firefox or Safari to see what it should look like

What is the expected output? What do you see instead?

---
In Internet Explorer the box doesn't have curvy corners. It should.

What version of the product are you using? On what operating system?

---
IE 8
Windows 7

Please provide any additional information below.

---
The W3C have practically finalised the specification for 'border-radius' 
and it contains all the features included in other implementations:
http://www.w3.org/TR/css3-background/#the-border-radius

In response to this, Webkit now supports the official 'border-radius' 
property:
http://webkit.org/blog/22/css3-goodies-borders-and-backgrounds/

I imagine Firefox may follow suit soon.

Original issue reported on code.google.com by robinwinslowmorris on 17 Mar 2010 at 1:50

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
CSS3 standard border-radius property supported by Chrome but not Safari - 
checked 
with latest Widnows download this very night. Given that curvyCorners must 
advise its 
users to adopt cross-platform portable code, we cannot advise people to drop 
the -
webkit- prefix yet. Also, Safari does not support the shorthand forms of the 
property, such as (-webkit-)border-radius 5px 3px 10px 20px;.

(I would like to imagine that Firefox/Safari would do anything soon. There are 
some 
important bugs I would like Firefox and Webkit to address. But I have to work 
on the 
hugely practical assumption that they won't.)

Agreed it seems silly - it *is* silly - but it isn't silliness on our part.

Original comment by c.1%smit...@gtempaccount.com on 20 Mar 2010 at 6:01