- Package:
- iceweasel
- Source:
- firefox-esr
- Submitter:
- Piotr
- Date:
- 2011-08-31 07:21:10 UTC
- Severity:
- normal
- Tags:
I am using a double screen configuration. My virtual screen resolution is 3320x1200 When I have my firefox open in the screen on right and try to type url, the hint appears too much on the left ( actually most of it goes to left screen) The same if I open a context menu... but only by clicking farther that the right screen width in the virtual screen. ( It looks like this.... but it can be some arbitrary boundry as well) For me it looks like some code preventing displaying menus outside visible area is broken. Unfortunately i was not able to take screenshot of this :( (Imagine right-clicking by mouse on the right part of a site and the menu displaying on the left side of screen.... always the same x position ! )
I use a laptop with an external monitor, using xrandr to add the new monitor when i plug it in and to remove it when i unplug. i'm seeing similar problems with iceweasel as the poster of #507897 describes, but in particular i'm seeing problems when the external monitor is *not* plugged in. in particular, menus should appear bounded by the current screen size (e.g. bringing up a context menu near the lower right of the screen should only open it near the edge of the screen, not hanging off of it) But in practice, the menus show up half-off the screen, with no way for the user to get to the errant menu options (except for blind kbd menu navigation, which i think we can agree is suboptimal). Here's my current screen resolution: 0 dkg@pip:~$ xrandr Screen 0: minimum 320 x 200, current 1024 x 600, maximum 1280 x 1624 VGA disconnected (normal left inverted right x axis y axis) LVDS connected 1024x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x600 59.5*+ 800x600 85.1 72.2 75.0 60.3 56.2 640x480 85.0 72.8 75.0 59.9 720x400 85.0 640x400 85.1 640x350 85.1 TV disconnected (normal left inverted right x axis y axis) 0 dkg@pip:~$ And attached is an image of a full-screen web-browsing session, where i've just right-clicked the page at the upper-left of where you see the context menu. when i use a single-screen configuration (no expanded size or options), the menu appears in a reasonable place, where i can see everything in it. when i'm in this potentially extra-screen situation, i get this problem. I haven't been able to determine yet whether it is worse if i start iceweasel when a second monitor is attached, or start X with a second monitor attached. i'm happy to do some debugging with this setup if you've got any suggestions for concrete steps to take. Thanks for maintaining iceweasel in debian!
I just did a little bit more debugging. From what i've seen, the menu errors i was reporting earlier seem to be a function of iceweasel starting up when the screen is at one resolution, and then persisting across a screen resolution change. In particular, if i start iceweasel when my screen is 1024x600 (single builtin LVDS), and then attach an external monitor (LVDS + VGA) to get a setup like this: 0 dkg@pip:~$ xrandr Screen 0: minimum 320 x 200, current 1280 x 1624, maximum 1280 x 1624 VGA connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.0*+ 75.0 59.9 60.0* 1280x960 60.0 1280x800 60.0 1152x864 75.0 1280x768 60.0 1024x768 85.0 75.1 75.0 70.1 60.0 59.9 832x624 74.6 800x600 72.2 75.0 60.3 59.9 56.2 640x480 75.0 72.8 72.8 75.0 66.7 60.0 59.9 720x400 70.1 LVDS connected 1024x600+0+1024 (normal left inverted right x axis y axis) 0mm x 0mm 1024x600 59.5*+ 800x600 85.1 72.2 75.0 60.3 56.2 640x480 85.0 72.8 75.0 59.9 720x400 85.0 640x400 85.1 640x350 85.1 TV disconnected (normal left inverted right x axis y axis) 0 dkg@pip:~$ then iceweasel prefers to show tooltips and menus still limited to the old 1024x600 resolution, even if the browser is running in the larger 1280x1024 display. this means that tooltips and menus that would otherwise be placed in reasonable spots in the righthand or bottom areas of the screen instead are placed in the small upper-left region. Conversely, if i start iceweasel when i have both screens attached and running, and then detach the larger screen, i get the problem i reported before: menus/etc end up displaying half off the screen to the point where i can't get to them. It's as though iceweasel is caching some information about the available display space at process start and failing to update that information when the available screen space gets resized. Hope this helps to track down the problem. Let me know if i can debug or test anything. Regards,
Hi, Sorry for the late answer. Did it get any better with Iceweasel 3.5.x ? Cheers, Mike
I commonly use dual-screen setup with one screen going on/off when I need it for other system. I did not experience any issues with Iceweasel menus in this setup (although I use them very rarely). My window manager probably unmaps/remaps/resizes the window every time I switch desktops so it might be that resizing or minimizing and restoring the window would fix the problem. A somewhat related issue I see is that when Iceweasel is running on one screen and it shows dialog on another screen the dialog size appears to be calculated as fraction of the size of the screen where the main windows is and then shown as fraction of the screen where the dialog is shown. That is if the main window is on a landscape screen and the dialog shows on a portrait screen it appears squashed, and the other way around. Also firefox sometimes fails to react to resize request from the window manager showing small content in a large window when the window is automatically maximized on startup and Ieweasel remembers smaller window size from last run.
Did it get any better with Iceweasel 5.0 (in unstable or from http://mozilla.debian.net) ? Cheers, Mike
Is it the same bug as this one or should I file a new bug? Drop-down menu from forms is placed in left top corner of he screen (instead of the right place) haldyr
Possible it's the same. What is your window manager?
As far as I know it should be kwin since I am running KDE 4.6.5. haldyr
I have to retract, it's not the same, I was thinking about bug 631176. Please followup there.