Closed Bug 11081 Opened 25 years ago Closed 25 years ago

XPMenus: View | Character Set too long to us

Categories

(Core :: XUL, defect, P3)

defect

Tracking

()

VERIFIED DUPLICATE of bug 9454

People

(Reporter: cpratt, Assigned: hyatt)

References

Details

Build ID: 1999080208 Platform: Linux and NT (and Mac OS, likely) To reproduce: - Launch apprunner - Select View | Character Set Result: The menu scrolls off of the bottom of the screen; on a 800x600 display, this means that the menu is too long to select commonly used character sets such as Cyrillic or Japanese. This is a big problem.
Target Milestone: M11
Assignee: trudelle → hyatt
Not MacOS so far, and the problem is that it _doesn't_ scroll or otherwise provide access to the menu items that don't fit on the screen. I don't have a feel for how important this is, pre-beta. Is any development work being held up? BTW, if these character sets are so commonly used, why are they at the bottom of a long menu? Could we reconfigure this menu, perhaps to use sub-menus, at least temporarily? reassigning to hyatt as p3 for m11
Status: NEW → ASSIGNED
Yes, this is a bug, but I'm compelled to point out that the charset menu sucks and should be fixed. It's ridiculous how big that menu is.
Depends on: 1877
I need the screen object implemented for this. Dependent on bug 1877.
Are you saying the screen object is not returning numbers? Because last I check it was returing proper numbers ( at least on windows, I haven't checked the GTK or Mac versions although those bugs were marked "fixed" ). The Avail routines are a bit optimistic about the size of the available screen real estate but that shouldn't be blocking you.
Ah. Vidur made a post on layout that made me think this wasn't implemented... so i can more or less get the screen resolution?
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
dup of 9454. this has to do with all xul popups. *** This bug has been marked as a duplicate of 9454 ***
Status: RESOLVED → VERIFIED
verified dup
You need to log in before you can comment on or make changes to this bug.