Opened 10 years ago

Last modified 3 years ago

#9075 assigned enhancement

BusyButton with type=submit doesn't submit form in IE

Reported by: coldwind Owned by: Kitson Kelly
Priority: high Milestone: 1.15
Component: DojoX Form Version: 1.3.0
Keywords: dojox.form.BusyButton Cc:
Blocked By: Blocking:

Description

It's because of disabling button in makeBusy method what preventing from submitting form.

May be it will be helpful to add property which will prevent from disabling button (and user will have to disable it in onsubmit event)?

Change History (10)

comment:1 Changed 10 years ago by dante

Owner: changed from dante to nonken

comment:2 Changed 10 years ago by bill

Milestone: tbd1.5

comment:3 Changed 9 years ago by Adam Peller

Milestone: 1.51.6

comment:4 Changed 8 years ago by bill

Milestone: 1.6future

(sadly) punting seemingly abandoned ticket and meta tickets to future

comment:5 Changed 6 years ago by Kitson Kelly

Owner: changed from nonken to Kitson Kelly
Status: newassigned

comment:6 Changed 6 years ago by Sébastien Le Ray

Same behavior on Chrome 25 with same cause. Simply replacing this.set("disabled", true) by window.setTimeout(dojo.hitch(this, "set", "disabled", true), 0); works perfectly.

comment:7 Changed 6 years ago by Sébastien Le Ray

After some testing, I realized the above fix disables the button if the cancel call is made following the makeBusy one (eg. no XHR between them). So you need to alter it to something like

window.setTimeout(dojo.hitch(this, function() { this.set("disabled", this.isBusy); }), 0);

This should do the trick.

comment:8 Changed 6 years ago by bill

#17205 is a duplicate of this ticket.

comment:9 Changed 4 years ago by dylan

Milestone: future1.12

This needs a patch with a pull request per our contribution guidelines ( https://github.com/dojo/dojo/blob/master/CONTRIBUTING.md ) if progress is going to be made on it. I don't think setTimeout is the right answer to solving the problem though.

comment:10 Changed 3 years ago by dylan

Milestone: 1.131.15

Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.

Note: See TracTickets for help on using tickets.