As I'm still on Cocoon 2.1.4 (so no Cocoon Forms, but it is the same problem there) I will use term "Woody" below.
I chose to use button elements instead of input elements for rendering wi:action as IE does not support the selection depending on attribute value (e.g. input[type="submit"]). Unfortunately IE does not behave that well then, all submits seemed to be sent at the same time: PARAM: 'add' VALUES: '[add object]' PARAM: 'repeater.first' VALUES: '[first]' PARAM: 'repeater.last' VALUES: '[last]' PARAM: 'repeater.next' VALUES: '[next]' PARAM: 'repeater.previous' VALUES: '[previous]' PARAM: 'woody_submit_id' VALUES: '[]' While with input/@type="submit" it is: PARAM: 'add' VALUES: '[add object]' PARAM: 'woody_submit_id' VALUES: '[]' The spec says clearly: "Buttons created with the BUTTON element function just like buttons created with the INPUT element, but they offer richer rendering possibilities." Seems not to be true for IE. Has anybody experience with this or circumvented in some way? Would it be possible to handle this via woody_submit_id, so that this value is always set and Woody gets the submit widget only depending on this value? WDYT? Joerg
