KO 2.1.0 Release Candidate 2

164 views
Skip to first unread message

Steve Sanderson

unread,
Apr 25, 2012, 5:25:59 AM4/25/12
to knock...@googlegroups.com
Hey

We were not planning to have a second release candidate for KO 2.1.0 before the final release, but since we decided to fix a couple of issues in 2.1.0 RC, here's (very hopefully) the final build: https://github.com/SteveSanderson/knockout/downloads (see Release Candidate 2).

This will only change if anybody discovers any new critical issues, so please let us know if you have any troubles with this new version!

Steve

Timothy Farrell

unread,
Apr 27, 2012, 2:40:59 PM4/27/12
to KnockoutJS
I think I found a bug. I'm not sure if it's a Chrome/Safari/IE bug or
a Knockout bug, but it's annoying. Basically using $index in
conjunction with radio buttons requires that the user has to click
twice. Here's an example of what I mean:
http://jsfiddle.net/explorigin/DFJ74/

The same thing without using $index :
http://jsfiddle.net/explorigin/XTcXG/

Tested in Chrome, Safari, IE9 (which exhibit the two-necessary clicks)
and Firefox (which works as expected).

Thanks,
-tim

On Apr 25, 4:25 am, Steve Sanderson <fla...@gmail.com> wrote:
> Hey
>
> We were not planning to have a second release candidate for KO 2.1.0 before
> the final release, but since we decided to fix a couple of issues in 2.1.0
> RC, here's (very hopefully) the final build:https://github.com/SteveSanderson/knockout/downloads(see Release Candidate

Michael Best

unread,
Apr 27, 2012, 4:05:31 PM4/27/12
to KnockoutJS
You should not use the *value* binding with checkbox or radio
controls. To set the value attribute, use the *attr* binding.

Here is your example, fixed:

http://jsfiddle.net/mbest/DFJ74/1/

-- Michael

Michael Best

unread,
Apr 27, 2012, 4:07:38 PM4/27/12
to KnockoutJS
Actually the *attr* binding should come before *checked* so that it
happens first:

http://jsfiddle.net/mbest/DFJ74/2/

Timothy Farrell

unread,
Apr 27, 2012, 4:16:20 PM4/27/12
to KnockoutJS
OK thanks. I see why now.
Reply all
Reply to author
Forward
0 new messages