Possible hover/dropdown menu bug

[Tomaso]

Issue:
Some hover/dropdown menus are very difficult to use in Pale Moon, as they seem to dissappear, before anything can be clicked.

Example:
http://www.boruitled.com/
(Try to use the "Products" menu, by letting your mouse pointer hover on it)

Mozregression result:
Last bad: Firefox v57.0a1 (2017-09-01)
First good: Firefox v57.0a1 (2017-09-02)

Note:
Although the menu, which I posted as an example, seems to be a tad sensitive, there's a clear difference between the FF builds above, whereas the "first good" release handles it much better.

FF pushlog:
https://hg.mozilla.org/mozilla-central/ ... 24da27fd58

--

(Tested with Pale Moon v28.5.0,x64 and v28.6.0a1,x64 (2019-05-24), under Win8.1Pro)

[Moonchild]

Bad menu design. If they want to do this then they must make sure there is overlap or at least no gap so the hover state remains active on the element.

[Tomaso]

Are you absolutely sure that it isn't allowed by some type of new and "forgiving" standard?
I only ask because I've encountered this issue several times, and other browsers seems to handle those type of menus much better.

Here's another example:
http://www.leathercelebrities.com/
(Try to use the "Celebrities" hover menu, at the top)
The Mozregression result is the same as the one that I posted before.

[Sajadi]

No problem in both sites with the unstable - using native user agent mode

[Tomaso]

No problem in both sites with the unstable - using native user agent mode

Are you sure that you've tested this properly.
The latest unstable has the same problem at my end, in all UA modes.

[Sajadi]

Of course. I know the effect which you describe. When you try to click on a menu item, it vanishes.

But in that 2 examples i have zero issues. I only have here ABPrime installed and no scripts blocked at all.

[jars_]

Of course. I know the effect which you describe. When you try to click on a menu item, it vanishes.
But in that 2 examples i have zero issues.

You're just too fast Just moving a little slower, then menu really disappears on going to menupopup.
I think Moonchild is right: Bad menu design.( not tested anywhere except chromium )

[Sajadi]

You're just too fast Just moving a little slower, then menu really disappears on going to menupopup.

Not really, i even took the time to make 1-2 seconds of pause before moving the cursor Still, works flawless.

[Lurker_01]

Not really, i even took the time to make 1-2 seconds of pause before moving the cursor Still, works flawless.

The problem is that there is gap of space between the button and the menu, if you move your mouse from the button to the opened menu too slowly it will disappear as it will register you are outside of the area of the button and the menu, i tried it with Vivaldi and on the sites menu's there is still a pixel gap that can make the menu disappear.
I agree just plainly bad menu design as it doesn't even work fine on chromium.

[Tomaso]

The problem is that there is gap of space between the button and the menu

Yes, Moonchild has already explained this.
But unfortunately, it's a somewhat common problem, which other browsers either seems to have an updated standard for, or a workaround (most likely).
If you try the two Firefox builds, which I mentioned in the first post, you'll notice that the latter one handles those type of menus much better.
However, since the menus apparently works flawlessly in Pale Moon for Sajadi, there are probably be some system dependent factors at work here too.

[Moonchild]

But unfortunately, it's a somewhat common problem, which other browsers either seems to have an updated standard for, or a workaround (most likely).

As other posts have already indicated this is NOT the case, as when the gap exists, other browsers do the exact same thing (including Chromium). The fact that you more readily see it in Pale Moon is likely just an indication that it is processing events faster and actually "hits" the gap with a pointer position update much more readily.

[Tomaso]

The fact that you more readily see it in Pale Moon is likely just an indication that it is processing events faster and actually "hits" the gap with a pointer position update much more readily.

OK.
I'd mark this issue as solved then, but it would seem that this particular feature is missing, after the last forum update.
Do you plan to reintroduce it?

[Moonchild]

Depends on if the extension dev can be bothered to make it compatible with 3.2