> * keyboard events / 0.9 merge

Alex and Scott checked in some keyboard fixes; Spec is at:  http://turboajax.com/dojo/key_compat.html

Decided to merge Adam's change (for dijit to run against core 0.9) ASAP.  Alex will give keyboard bugs stopping dijit high priority (and also high priority to other bugs that affect dijit)

We found one bug w/ENTER key (and probably other keys too) producing multiple keypress events on IE.

How to test for characters like ctrl-break is unclear? Does that set a keyChar or not?

> * radio button checkin?

Done!   Need to fix onclick handler.

Also questions about name of method for whenever the state changes.  onValueChanged() seems wrong (see below).  David will propose something.

Also questions on the standard getValue()/setValue() API as it refers to checkbox / radio.  David will write up some notes on the forum.

Since you can have radio buttons like this:

<input type=radio name=seat value=coach checked>

<input type=radio name=seat value=business>

<input type=radio name=seat value=first>

Then the meaning of getValue()/setValue() is not "checked/unchecked" but rather coach/business/first.   Therefore, need a getChecked() method or something.  Not sure.

> * onchange / onvaluechanged exact definitions (when do these events fire?)

Questions about firing every time the value of a node changes, vs just when it blurs.

David will write up some notes on the forum.

> * combined event for click or keyboard selection?

Decided yes, combined event called onclick, that's fired even when you "click" a button via the keyboard.

> * validateTextbox - get rid of missing message?
>

Didn't get a chance to discuss

> Status updates:

Koranteng has LayoutContainer and SplitContainer working against Adam's branch.   Will check in after merge.

> Button

Doug and Torrey talked about Button design; Torrey will try changing the CSS to use a background image so you don't need to have a <div> around the <button> node.   Doug will check in hopefully tomorrow.

Doug wanted to change the public api for form widgets to remove enable()/disable() and instead support setDisabled(boolean); I asked him to post a note to the developer forum.   It's not a big deal either way but I don't want to present two APIs to the user.