Home > Web Development > CurvyCorners 2.0.4 Released!

CurvyCorners 2.0.4 Released!

I have just released version 2.0.4 of CurvyCorners. The JavaScript library for adding rounded edges to your HTML boxes.

This new version brings a whole host of bug fixes and compatibility improvements with 3rd party libraries.

CurvyCorners Website

CurvyCorners Website

To use just include the javascript in the head section of your webpage and then add the following in your CSS file.

-moz-border-radius:3ex;
-webkit-border-radius:3ex;

Download: http://www.curvycorners.net
Usage: http://www.curvycorners.net/instructions/

Bookmark and Share

Cameron Web Development , , , ,


  1. Calvn
    November 15th, 2009 at 09:42 | #1

    Hi,

    I found that the curvycorner script has some problem with google adsense ads when using IE 8.

    I tried to put a text link ad inside a , of course the is rounded by the script, once I upload on to web, the text link ad just disappear after everything is load up.

    In FF & chrome & safari look alright.

    Is there any way to solve it? I think there is a bug or clash with the curvycorner script and google adsense ad javascript.

    Hope you address to this matter.

  2. February 22nd, 2010 at 05:25 | #2

    Hi, Cameron.

    CurvyCorners is absolutely amazing — thank you.

    I realized that each time I come to the site and try to navigate using the links containing anchors at the top of the instructions page, I’m whisked away to the home page that doesn’t have the relevant info on it at all. And I only just noticed today that that’s because your anchors at the top of /instructions are taking people to the home directory.

    Like, “Getting the Source” takes me to curvycorners.net/#source instead of curvycorners.net/instructions/#source like I think you intend. To format links on the same page, just use “#source” as the location instead of entering a full URL before it or using any forward slashes. (However, I see that your anchors ARE set up that way, so without further investigation, I have no idea why the links themselves are taking users to another page.) Something to look into when you have a moment?

    Thanks again for this awesome script!

    ~ Harmony

    • Cameron
      February 22nd, 2010 at 12:53 | #3

      Thanks for your kind comments. The anchors are slightly more complicated than it first appears. Basically the content of that page is pulled directly from the documentation of the latest build of CurvyCorners stored in the SVN repository on Goggle Code. The anchors are relative as they should be but I’m resetting the base URL of the page using the <base href=”" /> tag in the head of the website. If I set the anchors to absolute which would fix the problem, clicking on the same links in the documentation from the SVN would redirect the user to the website’s anchor and not the one on the standalone document.

      I’ll look into a work around when I get some time though as this needs to be fixed.

  3. Bobo
    February 24th, 2010 at 12:31 | #4

    I tried to email you with a few minor bugs/issues I noticed while using CurvyCorners, but it seems the contact email address on the curvycornets.net page isn’t working anymore.

    Below, the contents of the mail I sent:

    First of all, thank you very much for creating the curvycorners script. It has been very useful and a pleasure to work with.

    In using the script, I found two minor issues, one of which I have a fix for.

    The first issue is in css in nested classes. The script fails if I have a definition like:

    .classA .classB { -webkit-border-radius: 8px; }

    I have fixed this by changing line 311 in the source from (linebreaks added by me)

    boxCol = boxCol.concat(
    curvyCorners.getElementsByClass(argbits[1], encloser)
    );

    to

    boxCol = boxCol.concat(
    curvyCorners.getElementsByClass(argbits[1], encloser[j])
    );

    The second issue occurs when defining multiple corners in a single statement. The following CSS causes an error:

    .classA { -webkit-border-radius: 8px 8px 0 0; }

    This can easily be worked around by using seperate definitions for each corner, but it might be worth fixing anyway.

  1. No trackbacks yet.