Fun Firefox Bug
-
Just came across a fun Firefox bug unplanned feature. If I create a page with lots of content that causes the page to scroll, but I use CSS to set the overflow-y to hidden (and a DIV with 100% width/height on top of that content), most browsers will remove the scrollbar and the ability of the user to scroll. But not Firefox. If you use the mouse wheel or you try to scroll by highlighting the content down the page, all browsers work fine (that is, they don't scroll). Only, in Firefox, you can still scroll by using the PAGE DOWN and DOWN buttons. Guess users will just have to deal with a slightly sub-optimal splash screen.
-
Just came across a fun Firefox bug unplanned feature. If I create a page with lots of content that causes the page to scroll, but I use CSS to set the overflow-y to hidden (and a DIV with 100% width/height on top of that content), most browsers will remove the scrollbar and the ability of the user to scroll. But not Firefox. If you use the mouse wheel or you try to scroll by highlighting the content down the page, all browsers work fine (that is, they don't scroll). Only, in Firefox, you can still scroll by using the PAGE DOWN and DOWN buttons. Guess users will just have to deal with a slightly sub-optimal splash screen.
So, is it a bug or firefox attempting to comply with the user's ability to use the web the way he wants instead of an ill-bred developer trying to exert unwarrented control in their lives? :laugh: Now, I have to admit, I'd like to place that window I can't get rid of,devoted to ads I'm not interested in, and blocking real content from being shown to eternal oblivion. IE won't let me do that. So, should I be mad at IE for doing what the designer wants, or the designer for wanting to do that to me? I've been swearing at the designer. Maybe I should be swearing at IE for not listening to my needs?
-
Just came across a fun Firefox bug unplanned feature. If I create a page with lots of content that causes the page to scroll, but I use CSS to set the overflow-y to hidden (and a DIV with 100% width/height on top of that content), most browsers will remove the scrollbar and the ability of the user to scroll. But not Firefox. If you use the mouse wheel or you try to scroll by highlighting the content down the page, all browsers work fine (that is, they don't scroll). Only, in Firefox, you can still scroll by using the PAGE DOWN and DOWN buttons. Guess users will just have to deal with a slightly sub-optimal splash screen.
AspDotNetDev wrote:
scroll by highlighting the content down the page, all browsers work fine (that is, they don't scroll)
I am retracting this statement. It seems that you can use this technique to scroll in IE/Chrome (you just need some text to "grab" to start the scroll). The only browser it doesn't work in is Firefox. :doh:
-
Just came across a fun Firefox bug unplanned feature. If I create a page with lots of content that causes the page to scroll, but I use CSS to set the overflow-y to hidden (and a DIV with 100% width/height on top of that content), most browsers will remove the scrollbar and the ability of the user to scroll. But not Firefox. If you use the mouse wheel or you try to scroll by highlighting the content down the page, all browsers work fine (that is, they don't scroll). Only, in Firefox, you can still scroll by using the PAGE DOWN and DOWN buttons. Guess users will just have to deal with a slightly sub-optimal splash screen.
What you are trying to accomplish is the kind of thing I absolutely hate most about websites. Expect me to shun and blacklist any sites using that technique. Seriously.
-
Just came across a fun Firefox bug unplanned feature. If I create a page with lots of content that causes the page to scroll, but I use CSS to set the overflow-y to hidden (and a DIV with 100% width/height on top of that content), most browsers will remove the scrollbar and the ability of the user to scroll. But not Firefox. If you use the mouse wheel or you try to scroll by highlighting the content down the page, all browsers work fine (that is, they don't scroll). Only, in Firefox, you can still scroll by using the PAGE DOWN and DOWN buttons. Guess users will just have to deal with a slightly sub-optimal splash screen.
Why are you using a splash screen on the web? Splash screens are annoying wastes of bandwidth. Why would you deliberately put content outside the viewable window if you don't want people to scroll? Sounds like if you had a better planned website you wouldn't run into unplanned features.