Comments on: CustomInput Class: Accessible, Custom-Styled Checkboxes and Radio Buttons http://pipwerks.com/2010/03/11/custominput/ E-Learning and Web Development Sat, 27 Apr 2013 02:42:47 +0000 hourly 1 By: philip http://pipwerks.com/2010/03/11/custominput/#comment-1827 philip Wed, 12 May 2010 15:32:42 +0000 http://pipwerks.com/?p=885#comment-1827 @emilime good catch. I don’t think the original Filament code checked for initial state, but it makes sense to add it.

]]> By: emilime http://pipwerks.com/2010/03/11/custominput/#comment-1825 emilime Wed, 12 May 2010 13:51:34 +0000 http://pipwerks.com/?p=885#comment-1825 There is a little bug in the script: it ignores the initial value of checkbox/radio

so I’ve added:

if(input.checked) {
label.addClass(checked);
}

in the init for loop, now it’s perfect ;-)

]]> By: pipwerks » Providing the same UI across browsers http://pipwerks.com/2010/03/11/custominput/#comment-1776 pipwerks » Providing the same UI across browsers Thu, 08 Apr 2010 07:25:05 +0000 http://pipwerks.com/?p=885#comment-1776 [...] Jilion’s work comes from the same school of thought that led designers/developers to change the look and feel of other built-in browser components such as radio buttons and checkboxes. (Guilty!) [...]

]]> By: pipwerks » A new removeClasses utility for MooTools http://pipwerks.com/2010/03/11/custominput/#comment-1741 pipwerks » A new removeClasses utility for MooTools Sun, 14 Mar 2010 07:00:28 +0000 http://pipwerks.com/?p=885#comment-1741 [...] addClass and removeClass functions, which I use all the time. However, when I was working on my CustomInput class the other day, I discovered a major shortcoming of MooTools’ removeClass function — it [...]

]]>