-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Popup position in firefox #182
Comments
Screenshot? Browser version? OS? User-agent string? |
also, Slackin version? |
You can view it with Firefox at www.therms.io
|
@laughinghan any thoughts? |
Gif recording: http://recordit.co/beDRvESpMK/gif/notify |
…patibility. fixes rauchg#182.
The issue here is that Using |
…patibility. fixes rauchg#182.
…patibility. fixes rauchg#182. document.documentElement is no more cross-browser than .body. Switching to window.scrollY, with a fallback to docbody for IE.
…patibility. fixes rauchg#182. document.documentElement is no more cross-browser than .body. Switching to window.scrollY, with a fallback to docbody for IE.
I see you added window.scrollY/X - This still doesn't fix the popup. rendering to the stop of the page |
@crobinson42 - interesting. It worked on our install. documentElement had chrome issues, but |
I just manually added those 2 lines, maybe I should try a new install. I’ll let you know. Thanks. |
rauchg#226) * update from document.body to document.documentElement for Firefox compatibility. fixes rauchg#182. * document.documentElement is no more cross-browser than .body. Switching to window.scrollY, with a fallback to docbody for IE.
rauchg#226) * update from document.body to document.documentElement for Firefox compatibility. fixes rauchg#182. * document.documentElement is no more cross-browser than .body. Switching to window.scrollY, with a fallback to docbody for IE.
I'm experiencing an issue with the popup rendering at the top of the page when the snippet and iframe for slackin is located at the bottom of the page.
This issue is only experienced in Firefox.
The text was updated successfully, but these errors were encountered: