Mozilla.org web-page menu not usable when page is narrow, such Firefox for Android
Using Firefox 14.0.1 for Android.
1) Go to tab menu & choose to visit new page.
2) Choose bookmarks, and select About Firefox.
3) Choose FAQ (or one of the other pages).
When the page comes up, at the top I see a square block of thick lines indicating a web page menu, but when I touch it the menu appears VERY briefly and I have not yet discovered a way to see its contents or use it. Is there a way to navigate and use the menu?
[EDIT: I edited my question a bit to make it a bit more clear.] [EDIT: I edited the title based on the excellent feedback!]
I replicated the same issue using a Google Chrome browser.
I was able to add the userContent.css file with the code described below to a DESKTOP version of FireFox. HOWEVER I cannot yet find a way to add that file to the Android version. (There may be, I just haven't found it. The about:support page button that SHOULD open the preferences directory does nothing on my phone.)
I opened Mozilla Bugzilla bug 776622 against the Mozilla web site, as that's the REAL place to fix it.
この投稿は conwaytwt により に変更されました
すべての返信 (4)
I was hoping to hear from other folks running Firefox for Android. I really don't believe this is a virus; I believe I may have either encountered a bug or a feature I don't yet know how to use. Thank you for taking the trouble to respond.
Hi conwaytwt, I can replicate that problem. Actually, that menu just appears to be goofy. If you go to that page (http://www.mozilla.org/en-US/firefox/.../faq/) in your desktop Firefox and narrow the window until it switches to that menu (less than about 750 pixels), it behaves in an equally illogical manner.
If I use the DOM Inspector then I see a short change of the #nav-main-menu style attribute, but the change to display: block doesn't last and reverts back to display:none
This code in userContent.css keeps the menu open for me.
@-moz-document domain(www.mozilla.org){ #nav-main .toggle.open+#nav-main-menu { display:block!important; } }
Thanks for the EXCELLENT replies! I confirmed the problem in desktop Firefox and Google Chrome. I also confirmed the workaround in Firefox. Because I can't find a way to apply the workaround to my Android phone I'm not going to mark this one solved until Mozilla updates their web site -- I entered a comment and opened bug 776622 in Mozilla Bugzilla.