-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Field undefined when trying to listen on it #9175
Comments
Hmm, I checked out your linked PR. I'm wondering if it makes more sense to return early from the method if the element has not been cached, rather than process it. In the context of that intersection observer, if an element hasn't been previously cached then it likely shouldn't be triggering the update in either regard... it might not be entirely wrong to add the element to the list of autofill elements... but again, given the context of the intersection observer, we should only be re-evaluating visibility if the element has been previously found in the DOM. |
Resolved by #9279 |
error still present in chrome: Version 125.0.6422.113 (Official Build) (64-bit) |
Yes because the last release |
error still comes up chrome: Version 125.0.6422.142 (Official Build) (64-bit) BitWarden: 2024.5.1 |
in angula2 with zone "monkey patch" browser is also problem with this extension, site not working properly |
Steps To Reproduce
When navigating through views in some apps, this bug could happen.
More precisely, when an element appears and the url is changing at the same time (works in both orders).
It could be for example be triggered by a button.
Expected Result
Just to don't throw an error.
Actual Result
In file
bootstrap-autofill-overlay.js:4267
Screenshots or Videos
No response
Additional Context
Broken due to release
2024.4.1
, more precisely this commit : 77cfa8a#diff-8ff1ef69519807ae86fc872374b223656c9459d1b8b0304e8a2b602182b68f98R1349Operating System
macOS
Operating System Version
No response
Web Browser
Chrome
Browser Version
No response
Build Version
2024.4.2
Issue Tracking Info
The text was updated successfully, but these errors were encountered: