为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Dropdown list does not extend beyond the parent window frame limits

  • 6 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 jbellorg

more options

Hello everyone - I am facing a problem with drop-down lists under Firefox (v58) after switching from IE 11. When clicking on these fields to select values, the drop down list does not extend beyond the bottom of the page that it belongs to, Instead is stops at the very bottom of the parent page or is bumped upper to fit in the parent window, but still limited in size. This is very annoying for the users of an app that I support, especially since IE11 and Chrome do not have this issue (see screenshots attached). It seems that Firefox drop-down menus have to be contained within the frame boundaries of the window that is invoking them. Is this a known limitation or is there some settings that can be changed for these to behave like IE or Chrome? Thank you in advance for the help.

Hello everyone - I am facing a problem with drop-down lists under Firefox (v58) after switching from IE 11. When clicking on these fields to select values, the drop down list does not extend beyond the bottom of the page that it belongs to, Instead is stops at the very bottom of the parent page or is bumped upper to fit in the parent window, but still limited in size. This is very annoying for the users of an app that I support, especially since IE11 and Chrome do not have this issue (see screenshots attached). It seems that Firefox drop-down menus have to be contained within the frame boundaries of the window that is invoking them. Is this a known limitation or is there some settings that can be changed for these to behave like IE or Chrome? Thank you in advance for the help.
已附加屏幕截图

被采纳的解决方案

You have to check those meta-bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=1421229 https://bugzilla.mozilla.org/show_bug.cgi?id=1154677

If you didn't find similar to yours, just create a new one.

定位到答案原位置 👍 0

所有回复 (6)

more options

Hello,

To find the correct solution to your problem, we need some more non-personal information from you. Please do the following:

  1. Use ONE of these methods to open the Firefox Troubleshooting Information page:
    • Click the menu button New Fx Menu, click on help Help-29 and select Troubleshooting Information.
    • Type about:support into the Firefox address bar and press the enter key.
  2. At the top of the Troubleshooting Information page that comes up, you should see a button that says "Copy text to clipboard". Click it.
  3. Now, go back to your forum post, right-click in the reply box and select Paste from the context menu (or else click inside the reply box and press the Ctrl+V keys) to paste all the information you copied into the forum post.

If you need further information about the Troubleshooting information page, please read the article Use the Troubleshooting Information page to help fix Firefox issues.

Thanks in advance for your help!

more options

Thanks for the quick reply. The requested info does not fit in the page so I am posting it via a link. About:Support Info

more options

This is a known problem.

In Firefox you can use the search tool for large dropdown lists, maybe it helps. https://www.ghacks.net/2017/01/21/firefox-53-search-in-large-select-fields/

more options

@TyDraniu - Thanks for the information. Since it's a known issue, do you know if this is something that the Mozilla team is likely to address in upcoming releases? Is there a place online where we can see if this issue is intended to be addressed?

The search tool is only a little helpful as some lists have a large number of entries and knowing all of them ahead of selecting cannot really be expected from my users.

more options

选择的解决方案

You have to check those meta-bugs:

https://bugzilla.mozilla.org/show_bug.cgi?id=1421229 https://bugzilla.mozilla.org/show_bug.cgi?id=1154677

If you didn't find similar to yours, just create a new one.

more options

@TyDraniu - Thanks for the insight. Happy to see that the problem is being worked on. I am marking the solution as provided since I now have means to follow up with the development team on the resolution.