April 10, 2015 at 23:30 UTC - Views: 1 #17599
Right after installing Weaver Xtreme version 1.1.2 onto version 1.1, the main horizontal menu options with cascade sub options would not display sticky allowing mouse over to the revealed options.
To Duplicate the Problem: Mouse over any always visible option with sub options available. Sub menu descends. On mouse out from visible item region, sub menu disappears.
Upon copying version 1.1 over the top of version 1.1.2, normal mouse hover and sub menu visibility returned to normal.April 10, 2015 at 23:32 UTC #21223April 10, 2015 at 23:34 UTC #21224scramblerModerator
Your linked site is using 1.1 and not showing any issue.
We need to see it running 1.1.2 with the problem to check what is going onApril 11, 2015 at 00:29 UTC #21225
I must not understand what you are describing.
Are you talking about sub-menus, and sub-sub-menus as indicated by arrows on your main menu?
EDIT – I’m seeing the issue on Safari, but not Firefox or Chrome. This is can be duplicated on my dev site with my own test site.April 11, 2015 at 00:51 UTC - Views: 2 #21227
I think you have the problem description correct. I mouse over Home, which has a sub menu and the sub menu options reveal. Then when I try to slide down to the first option, as soon as I mouse out of the LI element’s region, the sub menu hides again.Yes, I am using an up to date version of Safari, v8.0.4, on Mac OS X 10.10.2.On Chrome and Firefox the behavior is not seen and the menu functions as expected.My dev environment does not currently have the same plugin builds. I can quickly fix that and see if the issue remains. I can’t leave my prod in this condition.Would it be helpful to configure my Dev and would you need an account so you can check the plugins more easily? What else can I do Weaver?April 11, 2015 at 01:00 UTC #21228scramblerModerator
The first thing to do is clear all caches especially if you are using a cache plugin.
Then on the site that exhibits the problems, deactivate ALL non weaver plugin to see if the problem goes away. If it does, reactivate one by one to find the culprit.April 11, 2015 at 01:30 UTC - Views: 2 #21229
Set up dev to match. Not able to duplicate problem.All same plugins activated.Down to on page content differences.Checked a number of pages and same behavior on each.This is going to take me a little longer to duplicate.Backleveled production to Extreme v1.1.Will work out a copy of Prod for testing instead of “similar build”.April 11, 2015 at 02:21 UTC - Views: 1 #21230
It is some kind of Safari quirk. I’ve found exactly where the issue is, but don’t understand it yet. VERY hard to track down. It will take a code fix, but I need to understand what the problem code was supposed to do! Should have a fixed version in a couple of hours.April 11, 2015 at 02:27 UTC #21231
WOW Weaver, you ARE the man! Wish I was at your level. Thanks a huge bunch. Let me know when ready and I’ll test against my environment if you need a beta tester.April 11, 2015 at 02:37 UTC - Views: 3 #21232
The problem is some kind of incompatibility with Safari, and involves some added code for Weaver X-Plus compatibility. I will post a 1.1.3 here in about an hour, and submit the fixed version to WordPress.org.
Unfortunately, there is no other fix for this other than updating to 1.1.3. The issues seems to be confined to Menus with submenus on Safari.April 11, 2015 at 03:38 UTC #21233April 14, 2015 at 21:17 UTC - Views: 1 #21234
Weaver,I can confirm that on my Mac OS X 10.10.2 workstation with Safari (latest), Chrome (latest) and Firefox (latest) that the problem noted is no longer observed.Many thanks for the quick response.Best regards,Gene
- You must be logged in to reply to this topic.