-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible bug in fill-active-el
#646
Comments
Just happened again with Edge. Different error. First time happened at the beginning of the string. This time an extra "g" was inserted in the middle.
|
Happened again in a CI run on macOS JDK21:
|
I just noticed this sporadic failure on CI (notice the 2 gs in Loggin):
@dgr asked me to reopen this issue. |
More data from a failed CI run a few days ago. OS/browser was Windows Edge.
|
@lread , I'm not sure where you got the output for this one. Did you happen to notice the OS and browser? |
Another trace from MacOS Edge:
|
This seems to be Edge specific. At least, everything above that has a browser noted lists Edge. This may point to a bug with Edge that we need to workaround. Seems to be OS independent, as it has been seen on at least Windows and MacOS. |
Version
This was a private development branch, but the most recent common parent is 602e0ec.
Platform
bb tools-versions
reports:Symptom
Failure of a test. Browser was Edge. Rerunning the text resulted in success. You can see that the failure is the difference between "MyLogin" (expected) for the "login" field, versus "mMyLogin" (actual). This suggests that the field is not getting cleared properly. This might be a timing thing with Edge, or possibly a bug in the way that
fill-human-el
does the underlying filling of the text field.Reproduction
Difficult to reproduce. Monitor and see if it happens again, either with Edge (might suggest an issue with Edge timing that would require some browser-specific delays in the test suite for Edge, similar to what is done for Safari today) or another browser (would suggest a more subtle bug in
fill-human-el
, possibly with the semi-random "mistakes").Actual behavior
Does not fill in the field correctly and that it caught by the test suite.
Expected behavior
Should fill in the field correctly.
Diagnosis
Nope. Could not reproduce on subsequent runs.
Action
Will monitor for now and report if it happens again.
The text was updated successfully, but these errors were encountered: