himanshugarg834@ in order to triage this issue could you please help us with the  sample html page or test url, so that we can test this scenario from our end.

Thank You...

Hi,

Please go to this link:
https://jsfiddle.net/dkc1esdL/3/

I have created a sample fiddle with a DOJO Title Pane and HTML checkbox. I have also added the required logging statements on clicking of the checkbox.

To reproduce the issue:
1. Go to the link specified above.
2. Click on the checkbox placed in the title bar of the title pane.
3. Open console and observe the logging statements.

Also attaching the screenshots of the logging statements on two different versions of Chrome. The two different versions are 54.0.2840.99 and 55.0.2883.87.

The behaviour is correct on 54.0.2840.99 as you can see from the logging statements in screen shot.

Deleted: 54.0.2840.99.JPG 111 KB

	54.0.2840.99.JPG 111 KB View Download

Deleted: 55.0.2883.87.PNG 136 KB

	55.0.2883.87.PNG 136 KB View Download

Also, there is one more issue with DOJO checkboxes (I think it is the same as the one mentioned above). The behaviour of Dijit Checkboxes is has been inverted with the latest update.

To test, please go to this link:
https://jsfiddle.net/dkc1esdL/1/

Steps to reproduce are the same as mentioned above. And results are also the same, the behaviour is correct on 54.0.2840.99 and inverted on 55.0.2883.87.

Thank you.

Able to reproduce this issue on Windows 10, Ubuntu 14.04 and Mac 10.12.2 on chrome stable version 55.0.2883.87 and also in current canary version #57.0.2962.0
Issue is broken in M55. 

Bisect Info:
===========

Good build : 55.0.2875.0,  Revision Range -421703
Bad build  : 55.0.2876.0,  Revision Range -421986

After executing the per-revision-bisect script, i got the following CL's between good and bad build versions
===========================================
https://chromium.googlesource.com/chromium/src/+log/bd027238e7f3d3c8096c1a62e9063d8cbf5d8a80..902a3d6303dfbfd49a24173777afcb4b70234a17

The suspecting Change Log is :
-----------
https://chromium.googlesource.com/chromium/src/+/902a3d6303dfbfd49a24173777afcb4b70234a17

From the above CL suspecting the below change
---------------------------
Review-Url: https://codereview.chromium.org/2375493005

mustaq@- Could you please look into this issue, if it's related to your change?  if not could you please help us to reassign this issue to the right owner.

Just to update, still able to reproduce the issue on windows 7 using chrome version 57.0.2969.0.

mustaq@ could you please look into this issue.

Thanks,

Looks like a double event handling somewhere in dojo for this particular demo:
- All DOJO checkboxes seem working fine, both the UI and the "checked" values:
https://dojotoolkit.org/documentation/tutorials/1.10/checkboxes/demo/CheckBox.html

- In the demo in this bug, moving the checkbox out of the titlePane also makes it work.

This looks like a Dojo implementation issue: the checkbox works fine when not placed inside a titlePane. The "checked" state somehow depends on both pointerdown & mousedown handlers, which seems non-ideal, and that seems to break inside a titlePane.

Thanks for the update.

FYI: Your bug is labelled as Stable Release Block, please make sure to land the fix and get it merged into the release branch ASAP so we can take it for next week's Beta release for Desktop. Thank you!

Seems there is nothing to fix in Chrome. Dojo team is aware of the issue on their side for a while already, here is their bug:
  https://bugs.dojotoolkit.org/ticket/18932

We will keep this bug open to track the Dojo fix. Removing release-blocker tag.

Looking at this more, it looks like it was fixed back in Dojo 1.10.5.

See http://jsfiddle.net/dylan/k5agxn2g/1/ for example, which seems to work as expected in Chrome 55.

Thanks Dylan for confirming the Dojo fix.