One site that I use (www.pgdp.net) has an interface for selecting characters that operates via a dropdown selection list.
Prior to the upgrade to FF 16 everything worked fine, but now many users of FF16 on Windows are reporting issues.
With previous FF versions, since the selection boxes are near the bottom of the window, the dropdown list would actually go up (remaining within the window) so all entries were visible, rather than down. They still work that way in IE and Chrome. But in FF (since FF16) the lists always drop in the downward direction. Since they do not fit within the window, they are truncated and we can not see all the entries to select with the mouse. Instead, we need to use the scroll bar or arrow keys to see all the entries.
This is very inconvenient for our users. Since it worked properly before FF16, and many users are reporting the issue, we believe that something in the FF16 update has caused this problem.
I notice several recent reports in Bugzilla of lists erroneously opening in the up direction, rather than down. But if the list will not fit opening downward shouldn't it open upward like it has in the past (and does in all other browsers)?
I took a look at that site, but I did not see any dropdown menus on any of the pages I visited from there. There are lots of links, and a few scrolling lists, but no dropdowns. Exactly where are these dropdown menus?
You would have to join, and then select a project (in P1 if you just joined) to proofread, and then try proofreading a page in. It's on the proofreading and formatting task pages that the problem occurs. If you want to try it, it's the A/E/I/O/U/+ set of pulldown selections that are misbehaving.
[Edit: I could make a screen capture available from FF16 and from Chrome or IE to show how they work (and how FF used to work). And I can make the source for that frame available if it would help.]
Seems to be working fine here.
Igc2VsZWN0OiA8aW5wdXQgdHlwZT0idGV4dCIgdmFsdWU9IjYw MCIgb25jaGFuZ2U9ImRvY3VtZW50LmdldEVsZW1lbnRCeUlkKC dkcycpLnN0eWxlLm1hcmdpblRvcD10aGlzLnZhbHVlKydweCci PjwvcD4KPHAgaWQ9ImRzIiBzdHlsZT0ibWFyZ2luLXRvcDo2MD BweCI+CjxzZWxlY3Q+CjxvcHRpb24gdmFsdWU9InZhbHVlMSIg c2VsZWN0ZWQ+T3B0aW9uIDE8L29wdGlvbj4KPG9wdGlvbiB2YW x1ZT0idmFsdWUyIiBzZWxlY3RlZD5PcHRpb24gMjwvb3B0aW9u Pgo8b3B0aW9uIHZhbHVlPSJ2YWx1ZTMiIHNlbGVjdGVkPk9wdG lvbiAzPC9vcHRpb24+CjxvcHRpb24gdmFsdWU9InZhbHVlNCIg c2VsZWN0ZWQ+T3B0aW9uIDQ8L29wdGlvbj4KPG9wdGlvbiB2YW x1ZT0idmFsdWU1IiBzZWxlY3RlZD5PcHRpb24gNTwvb3B0aW9u Pgo8b3B0aW9uIHZhbHVlPSJ2YWx1ZTYiIHNlbGVjdGVkPk9wdG lvbiA2PC9vcHRpb24+CjxvcHRpb24gdmFsdWU9InZhbHVlNyIg c2VsZWN0ZWQ+T3B0aW9uIDc8L29wdGlvbj4KPG9wdGlvbiB2YW x1ZT0idmFsdWU4IiBzZWxlY3RlZD5PcHRpb24gODwvb3B0aW9u Pgo8b3B0aW9uIHZhbHVlPSJ2YWx1ZTkiIHNlbGVjdGVkPk9wdG lvbiA5PC9vcHRpb24+CjxvcHRpb24gdmFsdWU9InZhbHVlMTAi IHNlbGVjdGVkPk9wdGlvbiAxMDwvb3B0aW9uPgo8b3B0aW9uIH ZhbHVlPSJ2YWx1ZTExIiBzZWxlY3RlZD5PcHRpb24gMTE8L29w dGlvbj4KPG9wdGlvbiB2YWx1ZT0idmFsdWUxMiIgc2VsZWN0ZW Q+T3B0aW9uIDEyPC9vcHRpb24+CjxvcHRpb24gdmFsdWU9InZh bHVlMTMiIHNlbGVjdGVkPk9wdGlvbiAxMzwvb3B0aW9uPgo8b3 B0aW9uIHZhbHVlPSJ2YWx1ZTE0IiBzZWxlY3RlZD5PcHRpb24g MTQ8L29wdGlvbj4KPG9wdGlvbiB2YWx1ZT0idmFsdWUxNSIgc2 VsZWN0ZWQ+T3B0aW9uIDE1PC9vcHRpb24+Cjwvc2VsZWN0Pgo8 L3A+CjxwIHN0eWxlPSJtYXJnaW4tdG9wOjEwMHB4Ij4KPC9wPg ==
Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
Try to disable hardware acceleration in Firefox.
Safe mode does not help, which should mean it's not one of the extensions.
Turning off hardware acceleration does not help, either.
If the window is maximized the dropdown selection list does not occur at all, making the selection list useless. If not maximized, then the list drops downward (instead of upward as it should) and extends somewhat below the edge of the window, with scroll bars.
A screenshot of the truncated dropdown is available at http://dl.dropbox.com/u/3229599/dropdown.jpg
What changed in FF16 to cause this? And how do we get it fixed?
The problem is resolved in FF 17, so whatever bug caused the issue in 16 has apparently been fixed.