-
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
firebaseui-dialog too tall on chrome #806
Comments
Hi, thanks for reaching out. Does it work if you set a max height on the element that contains Firebase UI in your app? |
I looked into this issue. I tried it out in various browsers and Chrome v87 and it works as expected. This issue seems to manifest in Chrome v88. I speculate it is a bug in the latest version of Chrome. We have a potential fix for it. |
This should be fixed in the latest FirebaseUI-web release. |
This either isn't fixed, or the 'fix' seems to have developed a bug of its own. In the latest version of Chrome as of today, this same dialog appears (for me) suddenly way over to the left of the screen, with seemingly random absolute position numbers: I'm unable to tame this beast as it appears as a dialog overlaid on top of the rest of the page, so doesn't respect the flexbox rules in the place it 'should' be appearing (I.E: in the firebase auth div container like a regular Google Sign-in does) |
[REQUIRED] Describe your environment
[REQUIRED] Describe the problem
firebaseui dialog grows after sign-on success

Steps to reproduce:
complete sign-on w/ link, enter email address to continue (don't press enter), over mouse over script debug "pause execution button", press enter and rapidly click pause button.
Open inspector to view DOM.
Relevant Code:
firebaseui-web/stylesheet/firebase-ui.css
Lines 375 to 377 in 540ddc0
My interim fix
I haven't seen any side effects from overriding the height yet ~ but considering the comment already existing there ~ maybe implications elsewhere.
The text was updated successfully, but these errors were encountered: