Skip to content
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

Native scrollbars are visible in Firefox and IE #77

Open
asm0dey opened this issue Jan 29, 2014 · 5 comments
Open

Native scrollbars are visible in Firefox and IE #77

asm0dey opened this issue Jan 29, 2014 · 5 comments

Comments

@asm0dey
Copy link

asm0dey commented Jan 29, 2014

Example:
http://fonbet.asm0dey.cloudbees.net/

Just resize browser window to size, when table doesn't fit into screen (by height).

@yairEO
Copy link

yairEO commented Mar 23, 2014

your demo pages acts really weird. please create a JSBIN to show the issue.

@asm0dey
Copy link
Author

asm0dey commented Mar 23, 2014

I can't reproduce this problem in jsfiddle :(

@mylann
Copy link

mylann commented Apr 10, 2014

Having the same issue on Mac OS. Even the demo shows the native scrollbars: http://cl.ly/image/142M1h0C2l1K

@gilo
Copy link

gilo commented Apr 29, 2014

I have the same issue. Firefox 28 on OS X display both the native scroll track and bar along the antiscroll bar

@pirxpilot
Copy link
Contributor

I think that the problem here is that Firefox on OS X at some point started using overlay (A.K.A. lion style) scrollbars. For antiscroll to work properly we need to measure the scrollbar width. The code that does that is here.
However since new Firefox scrollbar 'floats' over the content its width is measured as 0. As a result antiscroll does not add any padding to .aniscroll-inner element that would hide the scrollbar, which in turn makes both scrollbars, native and antiscroll generated, visible.

In my component compatible fork I am using an ugly hack - adjusting the width of the scrollbar if its calculated witdth is 0. If someone wants to port it back here I can help.

If someone has a better idea how to properly fix it don't hold back ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants