#33385 closed defect (bug) (fixed)
Unable to create users in IE8
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 4.3 | Priority: | normal |
Severity: | normal | Version: | 4.3 |
Component: | Users | Keywords: | has-patch commit |
Focuses: | javascript, administration | Cc: |
Description
To reproduce:
- Navigate to
/user-new.php
in IE8 as an admin - Enter a new username
- Enter a new e-mail address
- Click "Add New User"
This results in the following errors:
ERROR: Please enter your password twice.
ERROR: Please enter the same password in the two password fields.
The same errors occur if you enter a custom password, or a custom weak password.
Attachments (5)
Change History (19)
#2
@
9 years ago
Could this be related to #32886? @adamsilverstein, @markjaquith, do you have time to look into it?
#3
follow-up:
↓ 6
@
9 years ago
propertychange
(IE8) fires on programatic changes, input
does not.
IE8 appears to be looping events and clearing pass2 in the event following the lastpass comment. This causes a password mismatch.
In 33385.1.diff events are fired on the keypress event. It fixes the IE8 password mismatch but introduces a lag/stickiness with the strength meter status not changing immediately.
Needs iteration but I need to sign off now, I am afraid.
This ticket was mentioned in Slack in #core by obenland. View the logs.
9 years ago
#6
in reply to:
↑ 3
@
9 years ago
Good catch, I think I understand what was happening here with 'propertychange' which we were using to capture input in ie8.
I tried your patch in ie and and the only issue I still see is the delay in updating the password strength meter you mentioned.
Changing the method from keypress to keyup seems to have alleviated that to some degree, I'm still seeing an empty strength meter if i clear the password field in ie. I'm going to keep digging here to see if I can refine further.
Replying to peterwilsoncc:
propertychange
(IE8) fires on programatic changes,input
does not.
IE8 appears to be looping events and clearing pass2 in the event following the lastpass comment. This causes a password mismatch.
In 33385.1.diff events are fired on the keypress event. It fixes the IE8 password mismatch but introduces a lag/stickiness with the strength meter status not changing immediately.
Needs iteration but I need to sign off now, I am afraid.
#7
@
9 years ago
- Keywords dev-feedback added; needs-testing removed
In 33385.2.diff:
- Bind to
keyup
event, verified fires correctly across browsers (unlikekeypress
, fires after input value changes) - Added the ie8 equivalent css filter matching our opacity settings for the password strength meter.
Note: Because the password meter uses inline styles overriding the display
attribute, we are using opacity here to hide the password meter when the password field is blank. This doesn't work in ie8 where opacity
isn't fully supported - so you just get a blank box for the password meter. My patch includes a css filter that works in ie8, tested and it works correctly. An untested solution would involve a wrapper element that we could show/hide, not certain would even work though. Another option would be to leave the box as is for ie8, it looks like this:
#10
@
9 years ago
- Also address an issue with the cursor jumping to the end of the field when you edit the plaintext password.
#11
@
9 years ago
.4.diff
looks fine but $('#pass2').on( ...
doesn't have to change - for the sake of fixing the ticket, who cares, but it general...
Confirmed that IE9+ works correctly.