-
Notifications
You must be signed in to change notification settings - Fork 416
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
fa-bars get unresponsive when browser size is reduced #29
Comments
Hi, do you have any F12 Console errors being reported? I don't have this system to try an reproduce it. |
Hello,
However, these errors don't cause problem to the fa-bars button (and they happen anyway if i go to http://devoops.me/themes/devoops2/). Also, I tested with Chromium (Version 39.0.2171.65 Ubuntu 14.04 (64-bit)) and with this one, the button becomes unresponsive even if I reduce the browser size while accessing http://devoops.me/themes/devoops2/ Which browser/OS do you use? I would like to test it to compare. |
I'm on win 7 on chrome and ie11, it works as expected on the demo site and my own port that I use this theme on as well (i am not a dev, just another user like you). I've shrunk it down very thin and tried a few steps in between and it all works. |
We know problem with fa-bars(need some styling changes for small screen resolution). And we liked Firefox and Linux :) |
im having this problem, its working fine in a resized desktop browser and chrome on android device, but unresponsive (the whole breadcrumb bar is unresponsive) on iphone or you can try it on PC using chrome emulation mode in it's developer tools. |
Hello,
I am experimenting devoops using firefox 34 on Ubuntu 14.04 from file://path/index.html
Almost everything looks fine.
However, when I reduce the size of the browser to test how things will look in iPhone, the fa-bars button stops working. Then if I restore the original size of the browser, it starts working again.
I don't see this happening when I run the demos hosted at http://devoops.me/
Is there an explanation for this?
The text was updated successfully, but these errors were encountered: