JQuery Curvy Corners 2 Early Beta Available

I have uploaded a beta of JQCC2, based on the beta version 2.0 of the official script. This now includes support for jQuery 1.3.

There are still many optimisations to make and tests to perform, but the examples included in the zip work in IE6, IE7, Chrome, Safari, Firefox, and (excluding the CSS selector feature) Opera. My version does differ from the official script; mainly the fact that boxes are not fixed width/height.

If you find bugs, want to contribute fixes, or want to help extend the plugin please leave your comments.

Finally, special thanks to Terry Riegel, Cameron Cooke and Tim Hutchison who made the original CurvyCorners script; they did all the hard work!

Update: Beta 2 uploaded

Download: JQuery Curvy Corners 2 (1538)

Found this post useful? Why not buy me a coffee!

Related Entries

22 Responses to “JQuery Curvy Corners 2 Early Beta Available”

RSS feed for comments on this post.

  1. ndee says:

    Hi Mike,

    thank you for your continuing effort to make this plugin becoming better and better. You wrote above “JQuery 3.x”, do you mean 1.3.x? If yes, does the latest stable version not work with 1.3.x?

    Greets,
    ndee

    ReplyReply

    Comment made on March 21, 2009 at 11:12 am

  2. Mike Jolley says:

    @ndee: Whoops, thanks. This version works with 1.3, the the older one does not.

    ReplyReply

    Comment made on March 21, 2009 at 11:29 am

  3. ndee says:

    Hi again,

    I have troubles with this version. Using jQuery 1.3.2 in noConflict() mode. I get the following error “settings[cc].is.undefined” on line 341 (curvycorners.source.js) where it says }).height(settings[cc].radius + "px").width(settings[cc].radius + "px");

    Old version 1 with jQuery 1.2.6 works on the same site.

    If I replace every call of settings[cc].radius with a fixed size e.g. “8″ the curvy corners work with beta too. I do not know how to fix but it seems that the array is somehow out of scope when it is called.

    Thanks!

    ReplyReply

    Comment made on March 21, 2009 at 1:18 pm

  4. ndee says:

    @ndee: sorry my error, seems that the minification service i used produced the error. Works perfectly thanks.

    ReplyReply

    Comment made on March 21, 2009 at 7:00 pm

  5. VN Webdesign says:

    I’m using jQuery 1.3.2 in noConflict() mode. I got the following problem with this version:

    I did for primary-nav div with navigation structure like this:

    Item 1
    Item 2
    Item 3

    The background of primary-nav div is image background.

    The problem is all css inside primary-nav div be changed, and the background doesn’t appear in IE.

    Thanks!

    ReplyReply

    Comment made on March 22, 2009 at 7:16 pm

  6. Krist says:

    i seem to have found a curvy corner bug in google chrome.
    it’s the second time i used cc on a project but this is the first time this happened.
    if you look here, the rounded corners are colored red even when it isn’t specified in the css: http://hellowala.org/fss/cc/index_bug.html

    the fix i found was to apply an inline style to the cornered div to enforce the background color directive:
    http://hellowala.org/fss/cc/index.html

    the bug seems to disappear at random. like if I click on the link on the page, when I return back, the red color is gone. but the first time I load the page in chrome it’s sure to be there.

    ReplyReply

    Comment made on March 23, 2009 at 8:12 am

  7. Kai Sellgren says:

    Thanks for creating a fantastic script!

    ReplyReply

    Comment made on March 31, 2009 at 1:26 pm

  8. JJ says:

    The rounded element has its ID replaced with ‘ccoriginaldiv’ which breaks all styles that used the original ID as the selector.

    Also, the autoPadDiv needs to have overflow: hidden applied to it to properly wrap all floated content.

    Thanks for the work.

    ReplyReply

    Comment made on April 2, 2009 at 5:42 pm

  9. Chuck says:

    The script throws errors in IE8 using jquery1.3.2.

    jquery1.3.2 line 1065 Invalid agrument
    elem[ name ] = value;

    After a little debug session I determined your beta script tries to set the css value of paddingTop equal to “–7px” which is invalid.

    ReplyReply

    Comment made on April 10, 2009 at 7:51 pm

  10. Chuck says:

    The previous post should have shown 2 minus signs

    –7px

    ReplyReply

    Comment made on April 10, 2009 at 7:53 pm

  11. Chuck says:

    --7px

    Sorry for the duplicate posts…form post does not like the 2 minus signs in a row

    ReplyReply

    Comment made on April 10, 2009 at 7:54 pm

  12. Mike Jolley says:

    Thanks for the reports and fixes. Ill get to it when I have time :s

    ReplyReply

    Comment made on April 10, 2009 at 8:13 pm

  13. Chuck says:

    The w3c spec states that all padding values must be non-negative, therefore all padding values should be set after a call to Math.abs()…otherwise IE8 fails in standard mode.

    http://www.w3schools.com/css/pr_padding-top.asp

    ReplyReply

    Comment made on April 11, 2009 at 3:46 pm

  14. Chuck says:

    I have patched the beta and can send the changes. Shoot me an email.

    ReplyReply

    Comment made on April 11, 2009 at 3:58 pm

  15. Chuck says:

    There is also a layout issue when applied to a ul that has a repeating background image (the issue may apply to other containers as well)

    The ul in question has this css
    margin: 0;
    padding: 0;
    list-style-type: none;
    text-align:center;
    border-top: 1px solid;
    border-bottom: 2px solid;
    background-image: url('/templates/millstone1.0/images/dingbat1.gif');
    background-repeat: repeat;

    When cc is applied to the ul the top right and bottom right corners are inset by 2 pixels from the right border of the ul.

    I’ll see if I can determine the bug

    ReplyReply

    Comment made on April 11, 2009 at 5:53 pm

  16. Chuck says:

    The above layout issue is due to the different border style for top and bottom. If I remove
    border-top: 1px solid;
    border-bottom: 2px solid;

    and use

    border: 1px solid;

    the problem does not occur.

    ReplyReply

    Comment made on April 11, 2009 at 6:25 pm

  17. Rodrigo Barba says:

    I tried to ‘packer’ the script but not work… work only minified… :(

    ReplyReply

    Comment made on April 16, 2009 at 9:42 pm

  18. Eric Peters says:

    Would you mind uploading the project to github? I’d love to be able to fork/make some modifications and be able to send you a pull request?

    Might make for an easier method of keeping it updated letting the community chime in :)

    Regards,

    Eric

    ReplyReply

    Comment made on May 30, 2009 at 7:34 pm

  19. Mike Jolley says:

    @Eric Peters: I did not upload to github because I’m not familiar with it (command line stuff is over my head) – but I’m in the process of uploading to google code

    ReplyReply

    Comment made on June 2, 2009 at 1:09 pm

  20. Cynthia G says:

    If you experience the issue with Chrome displaying red areas, try moving the .css calls above the curvycorner .js in the head of the page.

    ReplyReply

    Comment made on October 28, 2009 at 10:29 pm

  21. B. says:

    The demos don’t work in IE8.

    ReplyReply

    Comment made on January 4, 2010 at 4:41 pm

  22. anagha says:

    @Chuck:

    Hi Chuck,
    Thanks for your finding . I am also getting 2 minus signs in roundcorner java script . could you please let me know where and what the solution you applied?
    I have jquery.curvycorners.source.js and service pack jquery.1.2.6.pack.js

    ReplyReply

    Comment made on January 5, 2010 at 10:11 pm

Leave a Reply

Why ask?

About this site

Blue Anvil is the online web design journal & portfolio of , a web designer from Norfolk, England. Read More »
ThemeSlice
  • Featured work - More

    • Beefjack
    • Integrity
    • theotaku.com
  • Latest Tweet - More

    • New blog post: MiniCard 1.1.7 Update http://blue-anvil.com/archives/minicard-1-1-7-update/
  • Out of the blue - More

    • MiniCard 1.1.7 Update

      I have just uploaded 1.1.7 of MiniCard here and to the WordPress theme directory. This updates includes:

      • New networks; xing, gowalla, yelp, foursquare, mobileme, google buzz
      • A way to change link text and define multiple links of the same network
      • A way to define your own custom links + icons
      • Improved admin panel

      Hope you like it, and don’t forget you can show your support by purchasing the premium pack from here.

    • Switched: From Shared to VPS

      It’s been about two weeks now since I made the transition from a shared reseller hosting account to a VPS (Virtual Private Server) account – impressions so far, excellent performance but fiddly to configure.

      The reason I wanted to change from shared hosting was the fact the server was always being hacked (even though ALL my scripts were secure), there was frequent downtime, support blamed me for problems every time, and it was slow as hell.

      Those used to a shared hosting environment would probably not know where to start when faced with configuring a VPS. Luckily, a lot of it was pre-configured when I received my account – certainly some of the major security holes were patched. I was not satisfied with those however. As a victim of hacking in the past (previous host swears it was not there fault, something I don’t believe) I took extra care to secure it as a much I could – configuring brute force detection, the firewall, installing mod security (excellent rules for that here: http://www.atomicorp.com/wiki/index.php/Atomic_ModSecurity_Rules) and going though multiple guides (like this one: http://www.webhostingtalk.com/showthread.php?t=468168) with a fine-tooth comb.

      The result? My pages are loading at least 6 times faster, I have had no down time (or at least have not noticed any), and I feel in control and happy. No longer am I at the mercy of shared hosts :)

      If your interested, I chose ServInt as my provider as they offered a great deal, as well as being a managed service (so I’m not on my own if I screw things up). I was tempted by the bells and whistles of Media Temple, but felt the ServInt service was better value.

    • Download Monitor 3.2.2 Maintenance Release

      Download Monitor has received some more love and has been updated. Here’s the change log from the new version:

      • Small bugfix in uploader.php – cat ID
      • Changed stats graph calculation – thanks lggemini
      • Changes to headers in download.php to avoid caching
      • File Browser fixes – $root was clashing with something….
      • exclude_cat works in all sections of download_page now
      • Removed hardcoding of /uploads/
      • Added action to download.php – should be able to use it to stop a download if you want – maybe limiting downloads per day or something? Whatever you want…
      • Made it so if you post new file on ‘edit’ screen, the post date is updated.
      • Fixed the ‘blank meta’ section which blanks out custom field values when nothing is set.
      • Moved ‘allow_url_fopen’ check.
      • Someone said downloads don’t work with spaces in the name. They do! Wasting my time sonny…
      • All work and no play make jolley a dull boy
      • Had to rename capabilities so they work. Apologies if you have to set this up again! Cheers to Mark Dingemanse.
      • {category_ID} custom format tag added. Useful if you want to send someone to its category on the DL page I guess. Also added {category_other} so when no category is set “other” is shown – this is because the download page can show an ‘other’ section if you want it to.
      • You can now manually edit the post date on the edit download screen.

      If you have edited capabilities for download monitor user permissions, you’ll have to again sorry! This is because I named them too long. Also, you should check your forced downloads still work because there was a logic error meaning they may not have been forced after-all…

      Enjoy.

    • Mahousive update to Download Monitor (3.2)

      Today I completed the update for the Wordpress Download Monitor Plugin – many tweaks, fixes, and features added. There were no changes to the database structure so people upgrading should be fine. Here is the list from the change log:

      • {user} tag added for custom formats
      • ‘autop’ option fix
      • Download page buttons applied with CSS so they are easier to customise/translate.
      • Fix for pagination bug after editing a download
      • Category output fix on edit downloads screen
      • Category urls on download page use ID rather than name to prevent errors when cats have the same names.
      • exclude_cat added to download_page shortcode
      • Localised ‘hits’ ‘date’ ‘title’ on download page
      • Option to disable the download logging
      • Read file ‘chunked’ some people found large files were corrupted so this should help (fingers crossed)
      • Added show_tags option to download page – displays x amount of tags on the download page.
      • File Browser root setting and download.php logic/mime types modified thanks to Jim Isaacs (jidd.jimisaacs.com)
      • Interface Improvements
      • Bulk edit categories, custom fields, tags, member only downloads
      • Added roles for download monitor admin – should be able to use with a role manager plugin if you want anyone other than admin to access the admin section e.g. http://wordpress.org/extend/plugins/capsman/
      • Change redirect after add
      • Edit Cat names/parents
      • Dedicated tags and thumbnails fields (they still use meta table though)

      And yes, those category link bugs are fixed at long last, and you can edit category names finally. Phew!