Opened 8 years ago

Closed 8 years ago

#9453 closed bug (notabug)

Click and Change events behaving differently in Firefox and Chrome

Reported by: dscain Owned by:
Priority: minor Milestone: none
Component: ui.button Version: 1.10.3
Keywords: Cc:
Blocked by: Blocking:

Description

Hi,

if you set events "click" and "change" after using the "button" widget to any "input", clicking on that "input" will cause:

Chrome Version 29.0.1547.22 beta-m: button will have "refresh()" (internal) executed before handlers of "click" and "change" are executed. Firefox 22.0: button will have "refresh()" (internal) executed BETWEEN handlers of "click" and "change" are executed.

My suggestion is that, although we shouldn't normally use "ui-state-active" but ":checked", having a different state between two browsers may introduce breaks in the future. I can't tell a specific case cause I did not went so far to understand how jquery-UI works internally, but having the same state for both elements is advised.

Here is a quick way to reproduce. They output should be the same for Chrome and for Firefox, and it is not, so try the code in both: http://jsbin.com/acuqah/3/edit

Change History (1)

comment:1 Changed 8 years ago by Scott González

Resolution: notabug
Status: newclosed

having a different state between two browsers may introduce breaks in the future

If that's your concern, then there's nothing we can do. The reason there's a difference is because the events occur in a different order in the two browsers. The button widget is responding to the change event, which occurs before click in Chrome and after click in Firefox.

Note: See TracTickets for help on using tickets.