#17205 closed defect (fixed)
dojox/form/BusyButton does not fire submit event in Chrome
| Reported by: | williambr | Owned by: | dante |
|---|---|---|---|
| Priority: | high | Milestone: | 1.8.8 |
| Component: | DojoX Form | Version: | 1.9.0 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: |
Description
Hello,
I hit a small bug. dojox/form/BusyButton of type submit does not fire the form "submit" event once it is hit, in Chrome. it works in Firefox, I did not test in other browsers.
This is new to 1.9.0, worked as expected in 1.8.x.
Here is an example: http://jsfiddle.net/umHBj/1/
Run in Chrome, click submit and it will not log the message set in "submit". Chaange it to Dojo 1.8.4, run it again and voila.
kitsonk in IRC told be to create it. I did not find anything related in trac as it is new with 1.9.0, so I'm sorry if it is a duplicate.
Thanks
Change History (13)
comment:1 Changed 8 years ago by
| Component: | General → DojoX Form |
|---|---|
| Owner: | set to dante |
comment:2 Changed 8 years ago by
comment:4 Changed 8 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Duplicate of #9075.
Thanks for catching that.
comment:5 Changed 8 years ago by
I am not sure this is a duplicated. How come it worked fine with 1.8.X and #9075 is from ages ago?
comment:6 Changed 8 years ago by
| Resolution: | duplicate |
|---|---|
| Status: | closed → reopened |
Now that you mention it, it does sound like a different bug.
comment:7 Changed 7 years ago by
Seems to be an issue with disabling the submit button in chrome. See this jsfiddle where it's reproduced in pure javascript: http://jsfiddle.net/5zLj7yug/
comment:8 Changed 7 years ago by
Proposed fix: https://github.com/dojo/dojox/pull/139
In the mean time, a workaround is to manually submit the form when the button is clicked.
comment:9 Changed 7 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:13 Changed 7 years ago by
| Milestone: | tbd → 1.8.8 |
|---|---|
| Priority: | undecided → high |
Backported to 1.8 (fix did not cleanly apply to 1.7)
I can confirm this one. One of my customers recently stepped over this bug, now he changed to firefox portable for the next few days. I will maybe have a look into the source code to help you out, when i am back in my office today (comparision of 1.8.4 and 1.9.x may help me with this i hope)