Menu items disappear when hovering
-
The two reports I heard were both from Linux - one from Mint and one from Fedora.
If you are using Chrome, try Chromium or vice versa. Alternately, try Google's binaries instead of those from your distro's package manager.
Add me to the list running Fedora (19 x86_64) and having the problem with Chrome. I am using the official repository from google. The menus work fine when connecting to 2.0.3 versions of pfsense. All versions of 2.1 so far exhibit the issue. Pain in the arse it is :). I spend sometimes 10 seconds just trying to get it to select a menu option. I have just been delaying reporting it because it seemed like I was the only one experiencing it based on lack of threads about it. Since I don't know what is causing it I was hoping the upgrade to Fedora 19 (fresh install actually) would fix it a few days ago but it didn't.
google-chrome-stable-28.0.1500.71-209842.x86_64
The yum config in case anyone is wondering:
[google-chrome]
name=google-chrome
baseurl=http://dl.google.com/linux/chrome/rpm/stable/x86_64
enabled=1
gpgcheck=1I actually have a new thread window opened with the title of "Drop down menus and Chrome" that I have been waiting to fill out and send… Looks like my procrastination has paid off... someone did it for me.
UPDATE: I just installed the latest fedora chromium and it has the same issue.
chromium.x86_64 0:27.0.1453.93-2.fc19
-
My Ubuntu laptop is running Chromium 28 from Ubuntu's repo and it's fine. FreeBSD is also on Chromium 28.0.1500.71 and it's OK. I haven't tried the "official" Google version yet. It's off now, if I remember, I'll give it a run tomorrow, unless one of my VMs actually works at the moment, which would be shocking.
It seems odd that it only affects certain setups, but (almost?) entirely Linux builds.
Any other common threads?
My Ubuntu laptop is 32-bit, FreeBSD is 64-bit. I build the FreeBSD one from source, Ubuntu laptop uses the Ubuntu package repository.
-
Also have any of you with problems completely cleared your cache in Chrome?
-
For me I installed the OS completely from scratch (for other reasons). There was no cache at all and I accessed the pfsense site first thing. When I just installed chromium it was also the first run of the browser so it's cache was empty too.
Now that i think about it though, I am going through a squid proxy. I will clear the cache tomorrow and go direct to rule that out but this is an https SSL site and it is not doing any decryption at the proxy to analyze https content so the squid proxy will not be caching the pfsense content.
-
I wiped a VM and installed Ubuntu 13.04 fresh and was able to reproduce it with the official Google .deb for Chrome. And now my Ubuntu laptop offered a Chromium update and it does it there, too.
It must be specific to this version of Chrome on Linux. It did not do this previously and it doesn't seem to affect any other platform aside from Linux (Windows is OK, so is FreeBSD)
Clicking on the menu bar before selecting the submenu does seem to work around it at least.
Has anyone reported it upstream, or looked for similar existing bug reports?
If someone can find an HTML change that can be made to "fix" it on pfSense, it would also be considered.
-
Has anyone reported it upstream, or looked for similar existing bug reports?
Report upstream? With bugs handling like this or this, no, thanks, I have better things to do with my time than wasting time with utterly moronic upstream who's only action is go Restrict-AddIssueComment-Commit once too many people have complained about the developers being morons.
-
Clicking on the menu bar before selecting the submenu does seem to work around it at least.
That work around doesn't really work reliably for me (it does sometimes). I usually have to go back and forth between moving the mouse over the menu bar and where the menu would open to several times at different speeds until the menu finally stays open for that time. If I keep going up to the menu though it will stop working again. When it gets to me I just use Firefox but I don't have many firewalls on 2.1 yet.
If I move the mouse cursor up to the menu and down at my normal slower mouse movement speed it doesn't work very often (25% of the time). If I quickly move the cursor up to the menu and down at very fast speed all in one quick motion it works about 80% of the time.
UPDATE: If i go very slow it will work near 0% of the time. On pfSense 2.0.3 it works every time regardless of course.
-
The speed thing works here too, and adds to the weirdness.
So it seems to be:
OK:
FreeBSD chromium-28.0.1500.71 (Compiled from source)
Windows Chrome 28.0.1500.95 m
OS X Chrome 28.0.1500.71
OS X Chrome 28.0.1500.95 (Tried before and after an update wanted to run)Broken:
Chromium 28.0.1500.71 Built on Ubuntu 13.04, running on LinuxMint 15 (28.0.1500.71-0ubuntu1.13.04.1) - Installed from Software Manager
Chromium 28.0.1500.71 Ubuntu 13.04 (28.0.1500.71-0ubuntu1.13.04.1) - Installed from Software Center
Chrome 28.0.1500.95 - On Ubuntu and Mint - Installed from the .deb provided by Google -
Add to OK: Chrome 29.0.1547.32_beta213282 from source (Gentoo amd64). This Chrome gets updated pretty regularly and I can't ever recall a problem in the 28 series either.
Just tried a test vm I have lying around with stock Ubuntu 13.04 on it - Chromium 28.0.1500.71 - nearly OK. The VM was accessed directly using its "console" through the vSphere client. There could be a timing issue of some sort on the menus. I can recreate the issue if I move my mouse too fast or in the wrong way - hard to explain but my Gentoo physical box has no problems whatsoever. It may be worth looking at the window manager. It generally works OK if I hover over the menu title for a second and then move to the menu item. The VPN menu is the least reliable for me perhaps because it has the shortest title.
Cheers
Jon -
The speed thing works here too, and adds to the weirdness.
So it seems to be:
OK:
FreeBSD chromium-28.0.1500.71 (Compiled from source)
Windows Chrome 28.0.1500.95 m
OS X Chrome 28.0.1500.71
OS X Chrome 28.0.1500.95 (Tried before and after an update wanted to run)Broken:
Chromium 28.0.1500.71 Built on Ubuntu 13.04, running on LinuxMint 15 (28.0.1500.71-0ubuntu1.13.04.1) - Installed from Software Manager
Chromium 28.0.1500.71 Ubuntu 13.04 (28.0.1500.71-0ubuntu1.13.04.1) - Installed from Software Center
Chrome 28.0.1500.95 - On Ubuntu and Mint - Installed from the .deb provided by GooglePlease add as broken Safari 6.0.5 on OSX 10.8.4 with 1Password extension while Chrome 28.0.1500.95 with same extension works fine. Without extension Safari works fine. I think it is a scripting problem.Edit: not very obvious, but I was using a non-native resolution on my iMac screen. When I switched to native resolution the problem was gone.
