I did not observe this on my local copy of gEAR but observed it on production and devel. If the user goes to "User Profile" after logging in, and attempts to check either the "colorblind mode" or "want updates" checkboxes, it triggers the "matching password" check where the new password and the repeated password have to match. Downstream this also changes the scope of the "save updates" CGI call where only the password is updated and not the checkbox information.
I believe there may be an unmatched HTML element somewhere, since the "matching" password check is only supposed to occur on a KeyUp event on the "new password" or "repeat password" HTML ids.
I did not observe this on my local copy of gEAR but observed it on production and devel. If the user goes to "User Profile" after logging in, and attempts to check either the "colorblind mode" or "want updates" checkboxes, it triggers the "matching password" check where the new password and the repeated password have to match. Downstream this also changes the scope of the "save updates" CGI call where only the password is updated and not the checkbox information.
I believe there may be an unmatched HTML element somewhere, since the "matching" password check is only supposed to occur on a KeyUp event on the "new password" or "repeat password" HTML ids.