-
Notifications
You must be signed in to change notification settings - Fork 15k
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
fix: <datalist>
dropdown positioning
#36934
Conversation
299df3c
to
b2b17ac
Compare
b2b17ac
to
1000d2d
Compare
Release Notes Persisted
|
I was unable to backport this PR to "22-x-y" cleanly; |
I have automatically backported this PR to "23-x-y", please check out #36959 |
Is this likely to be backported to 22.x.y or will we have to wait for the release of 23.x.y for a fix? |
This PR needs a manual backport. It is marked as targeting 22.x.y but the bot could not do it automatically. |
fix: datalist dropdown positioning
fix: datalist dropdown positioning
Do not plan to port this fix to 22.x.y? |
Description of Change
Closes #36906.
Refs #35628.
Fixes an issue where
<datalist>
elements were improperly positioned within the page. We had copied several helper functions out ofchrome/browser/ui/views/autofill/autofill_popup_view_utils.cc
and were usingCalculatePopupXAndWidthHorizontallyCentered
after having calledCalculatePopupBounds
.CalculatePopupBounds
itself callsCalculatePopupXAndWidthHorizontallyCentered
, so there's no need to do it twice.Tested with https://gist.github.com/e50cb256d567ed25b7bbf12b9cbe5417.
Before
After
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where
<datalist>
elements were improperly positioned within the page.