X
Nhấn vào đây để đến phiên bản di động của trang web.

Diễn đàn trợ giúp

Website Menus Disappear When Moving Mouse; Unable to Make Selection.

Được đăng

I can hover over the menu and it will display my submenus; however when I move my mouse in an attempt to select something from that submenu, the submenu disappears. Never able to select anything within the menu. I have tried running in Safe Mode, didn't resolve. This started the end of May 2019. There were no changes made to the website.

I can hover over the menu and it will display my submenus; however when I move my mouse in an attempt to select something from that submenu, the submenu disappears. Never able to select anything within the menu. I have tried running in Safe Mode, didn't resolve. This started the end of May 2019. There were no changes made to the website.
Trích dẫn

Chi tiết hệ thống bổ sung

Ứng dụng

  • Chuỗi đại diện người dùng: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0

Thông tin chi tiết

cor-el
  • Top 10 Contributor
  • Moderator
17424 giải pháp 157436 câu trả lời
Được đăng

Does this happen with all menus that open on hover or only on this specific website ?

Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)?

Can you attach a screenshot?

Does this happen with all menus that open on hover or only on this specific website ? Can you post a link to a publicly accessible page (i.e. no authentication or signing on required)? Can you attach a screenshot? *https://support.mozilla.org/en-US/kb/how-do-i-create-screenshot-my-problem *use a compressed image type like PNG or JPG to save the screenshot
Bài viết này có hữu ích với bạn không?
Trích dẫn

Người tạo câu hỏi

Only on this specific website. Referencing the screenshots, if I hover my mouse over any of the menu options (Accounts/Transactions/Services/Preferences/Sign Off), I can view the menu contents; however as soon as I move my mouse down to select something within the menu - for example Accounts->Overview, the menu disappears.

Only on this specific website. Referencing the screenshots, if I hover my mouse over any of the menu options (Accounts/Transactions/Services/Preferences/Sign Off), I can view the menu contents; however as soon as I move my mouse down to select something within the menu - for example Accounts->Overview, the menu disappears.
Bài viết này có hữu ích với bạn không?
Trích dẫn
cor-el
  • Top 10 Contributor
  • Moderator
17424 giải pháp 157436 câu trả lời
Được đăng

A possible cause is a small gap between the menu bar and the drop-down list. Sometimes you can workaround this by moving the mouse pointer as quickly as possible to the drop-down list.

A possible cause is a small gap between the menu bar and the drop-down list. Sometimes you can workaround this by moving the mouse pointer as quickly as possible to the drop-down list.
Bài viết này có hữu ích với bạn không?
Trích dẫn

Người tạo câu hỏi

The menus work fine in Chrome, IE 11 and Edge; however not in Firefox since May. Moving fast does not help.

The menus work fine in Chrome, IE 11 and Edge; however not in Firefox since May. Moving fast does not help.
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

Is there no answer to this problem as I am experiencing it as well. It works on every other browser except Firefox.

Is there no answer to this problem as I am experiencing it as well. It works on every other browser except Firefox.
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

Could one or both of you provide a link to a page demonstrating the problem. There are many ways to construct hover menus, and that would be more efficient than "20 questions."

Could one or both of you provide a link to a page demonstrating the problem. There are many ways to construct hover menus, and that would be more efficient than "20 questions."
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

Here is the link to the page that I am referring to. Keep in mind that this is the same link that I use in testing other browsers. I have tested it on Vivaldi, Edge, Chrome, and Waterfox. The drop down menu works on all of the other browsers. Menu Link

Here is the link to the page that I am referring to. Keep in mind that this is the same link that I use in testing other browsers. I have tested it on Vivaldi, Edge, Chrome, and Waterfox. The drop down menu works on all of the other browsers. [http://fredspools.somee.com/userLogin.asp Menu Link]
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

Thank you for the example. When the mouse pointer moves off the link, the script checks this:

// If the mouse has moved off the link but not onto the sub menu,
// close it.
if (!domUtils.contains(current, related) && !domUtils.contains(activeSubMenu, related))
  closeSubMenu();

In Firefox "related" is undefined. It is assigned here:

if (window.event) {
    current = this;
    related = window.event.toElement;
} else {
    current = e.currentTarget;
    related = e.relatedTarget;
}

Before around Firefox 65, Firefox would always run the code after else. Starting around Firefox 65, Firefox supports some aspects of window.event so the first two lines are running. Apparently Firefox does not support toElement so that is why related is no longer defined.

Are you able to edit this code or is this a platform file you can't edit? If you can edit it, we could suggest some changes.*


Note: individual end users can disable Firefox from using window.event by toggling a preference, but obviously this isn't practical for a website to explain to people. To test for yourself:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk.

(2) In the search box above the list, type or paste window.event and pause while the list is filtered

(3) Double-click the dom.window.event.enabled preference to switch the value from true to false

Reload the page before testing. Menus should work normally.


* EDIT: This is what I would try. I haven't tested it live.

if (e) { // standards compliant
  current = e.currentTarget;
  related = e.relatedTarget;
} else if (window.event) { // legacy
  current = this;
  related = window.event.toElement;
}
Thank you for the example. When the mouse pointer moves off the link, the script checks this: // If the mouse has moved off the link but not onto the sub menu, // close it. if (!domUtils.contains(current, related) && !domUtils.contains(activeSubMenu, related)) closeSubMenu(); In Firefox "related" is undefined. It is assigned here: if (window.event) { current = this; related = window.event.toElement; } else { current = e.currentTarget; related = e.relatedTarget; } Before around Firefox 65, Firefox would always run the code after else. Starting around Firefox 65, Firefox supports some aspects of window.event so the first two lines are running. Apparently Firefox does not support '''toElement''' so that is why related is no longer defined. Are you able to edit this code or is this a platform file you can't edit? If you can edit it, we could suggest some changes.* ---- Note: individual end users can disable Firefox from using window.event by toggling a preference, but obviously this isn't practical for a website to explain to people. To test for yourself: (1) In a new tab, type or paste '''about:config''' in the address bar and press Enter/Return. Click the button promising to be careful or accepting the risk. (2) In the search box above the list, type or paste '''window.event''' and pause while the list is filtered (3) Double-click the '''dom.window.event.enabled''' preference to switch the value from true to false Reload the page before testing. Menus should work normally. ---- ''* EDIT: This is what I would try. I haven't tested it live.'' if (e) { // standards compliant current = e.currentTarget; related = e.relatedTarget; } else if (window.event) { // legacy current = this; related = window.event.toElement; }

Được chỉnh sửa bởi jscher2000 vào

Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

Making the change to dom.window.event.enabled to false works...the menu now works as it should. Will leaving this setting at false cause other problems elsewhere?

As for your other question, the application in question is not mine, but I can edit it. Unfortunately, I am not a coder so unless you are very specific I probably would not be able to make any changes.

I appreciate your help on this.

Making the change to dom.window.event.enabled to false works...the menu now works as it should. Will leaving this setting at false cause other problems elsewhere? As for your other question, the application in question is not mine, but I can edit it. Unfortunately, I am not a coder so unless you are very specific I probably would not be able to make any changes. I appreciate your help on this.
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

I forgot to mention that editing the file would be preferable because I would not want to try to explain to others what needs to be done to fix the menu problem using the about:config option.

I forgot to mention that editing the file would be preferable because I would not want to try to explain to others what needs to be done to fix the menu problem using the about:config option.
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

Here's what I would suggest: flip the order. This would be a change to lines 190-197 of /scripts/common.js:

if (e) { // standards compliant
  current = e.currentTarget;
  related = e.relatedTarget;
} 
else if (window.event) { // legacy
  current = this;
  related = window.event.toElement;
}
Here's what I would suggest: flip the order. This would be a change to lines 190-197 of /scripts/common.js: if (e) { // standards compliant current = e.currentTarget; related = e.relatedTarget; } else if (window.event) { // legacy current = this; related = window.event.toElement; }
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

I made the change to the common.js script as you suggested and then went back to about:config and changed the dom.window.event.enabled to true and the menu does not work again. Am I supposed to keep the dom.window.event.enabled to false in order for this to work?

I made the change to the common.js script as you suggested and then went back to about:config and changed the dom.window.event.enabled to true and the menu does not work again. Am I supposed to keep the dom.window.event.enabled to false in order for this to work?
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

Obviously there's some other difference I or someone else needs to track down so it can work without a preference change.

Obviously there's some other difference I or someone else needs to track down so it can work without a preference change.
Bài viết này có hữu ích với bạn không?
Trích dẫn
cor-el
  • Top 10 Contributor
  • Moderator
17424 giải pháp 157436 câu trả lời
Được đăng

Note that you may have to use reload and bypass the cache to ensure fresh (updated) files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)
Note that you may have to use reload and bypass the cache to ensure fresh (updated) files. *hold down the Shift key and left-click the Reload button *press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux) *press "Command + Shift + R" (Mac)
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

Could you do the same replacement at lines 221-228 where window.event is checked again to set related?

Could you do the same replacement at lines 221-228 where window.event is checked again to set related?
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

jscher2000 said

Could you do the same replacement at lines 221-228 where window.event is checked again to set related?

Doing that eliminates any of the drop down links...all you see is the parent link.

''jscher2000 [[#answer-1240078|said]]'' <blockquote> Could you do the same replacement at lines 221-228 where window.event is checked again to set related? </blockquote> Doing that eliminates any of the drop down links...all you see is the parent link.
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

Here is what I have done: 1. Edited the common.js file as you suggested earlies (lines 190-197) 2. Went back and changed the dom.window.event.enabled to true 3. Deleted the cache in Firefox and used ctrl-f5 on the website

The result of these actions has allowed me to be able to click on the first link in the drop down menu and the other links disappear like it did originally.

Here is what I have done: 1. Edited the common.js file as you suggested earlies (lines 190-197) 2. Went back and changed the dom.window.event.enabled to true 3. Deleted the cache in Firefox and used ctrl-f5 on the website The result of these actions has allowed me to be able to click on the first link in the drop down menu and the other links disappear like it did originally.
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

Did I give the wrong lines?

When I save the page locally (Ctrl+s, Web page complete) and edit the common.js file, it works for me in Firefox. Uploaded here for the moment:

http://www.jeffersonscher.com/temp/login.html

http://www.jeffersonscher.com/temp/login_files/common.js

Did I give the wrong lines? When I save the page locally (Ctrl+s, Web page complete) and edit the common.js file, it works for me in Firefox. Uploaded here for the moment: http://www.jeffersonscher.com/temp/login.html http://www.jeffersonscher.com/temp/login_files/common.js
Bài viết này có hữu ích với bạn không?
Trích dẫn
fbonani1 0 giải pháp 15 câu trả lời
Được đăng

I just copied, saved, and uploaded the common.js file in your link and the my website drop down menus now work. I must have edited the wrong lines in the file because when I did a compare files, I could see that you had edited the file in different places. Thanks for your help.

BTW, how did you upload my website to your test site? That is a pretty nifty trick.

I just copied, saved, and uploaded the common.js file in your link and the my website drop down menus now work. I must have edited the wrong lines in the file because when I did a compare files, I could see that you had edited the file in different places. Thanks for your help. BTW, how did you upload my website to your test site? That is a pretty nifty trick.
Bài viết này có hữu ích với bạn không?
Trích dẫn
jscher2000
  • Top 10 Contributor
8642 giải pháp 70714 câu trả lời
Được đăng

fbonani1 said

BTW, how did you upload my website to your test site? That is a pretty nifty trick.

If you use Save Page As (Ctrl+s) and select Web page, complete, then you get a local file + folder of assets you can FTP anywhere. It's not always complete but fortunately it was complete enough in this case.

''fbonani1 [[#answer-1240093|said]]'' <blockquote> BTW, how did you upload my website to your test site? That is a pretty nifty trick. </blockquote> If you use Save Page As (Ctrl+s) and select Web page, complete, then you get a local file + folder of assets you can FTP anywhere. It's not always complete but fortunately it was complete enough in this case.
Bài viết này có hữu ích với bạn không?
Trích dẫn
Đặt một câu hỏi

Bạn phải đăng nhập vào tài khoản của bạn để trả lời bài viết. Vui lòng bắt đầu một câu hỏi mới, nếu bạn chưa có tài khoản.