We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

საიტის გასაუმჯობესებელი სამუშაოების მიმდინარეობისას, შესაძლებლობების ნაწილი შეიზღუდება. თუ სტატიით ვერ მოახერხებ ხარვეზის გამოსწორება და შეკითხვის დასმა გსურთ, ჩვენი მხარდაჭერის გუნდი დაგეხმარებათ @FirefoxSupport გვერდის მეშვეობით Twitter-ზე და /r/firefox განყოფილებაში Reddit-ზე.

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში მხარდაჭერის საიტზე. აქ არასდროს მოგთხოვენ სატელეფონო ნომერზე დარეკვას, შეტყობინების გამოგზავნას ან პირადი მონაცემების გაზიარებას. გთხოვთ, გვაცნობოთ რამე საეჭვოს შემჩნევისას „დარღვევაზე მოხსენების“ მეშვეობით.

ვრცლად

New windows created by links do not start maximized

  • 2 პასუხი
  • 8 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 4 ნახვა
  • ბოლოს გამოეხმაურა tieless

Currently using Firefox 37.0.1 on Windows 7 x64, but this issue has been present for a long time.

When clicking a link that opens a new window (ie a link using target="_blank") the new window does not open maximized. For example on the page http://www.protodave.com/tools/verifying-a-dkim-txt-record-and-key-length/ when you click the 'DKIM Key Checker' link it opens the target page in a new window. The window does not open maximized. I currently have Firefox customized with the Title Bar and Menu Bar showing and I do not have 'Open new windows in a new tab instead' checked.

There is a workaround for this issue and that is to disable the Title Bar in the customize menu. When the Title Bar is not enabled then new windows properly open maximized. The fact that Firefox produces the expected behavior when in the default no-title-bar state and produces undesired behavior in the title-bar-enabled state leads me to believe this is either a bug or (hopefully) an obscure about:config option that I have so far been unable to descry.

I prefer the Title Bar enabled and so I just live with the issue, but it is definitely aggravating. Please help.

Currently using Firefox 37.0.1 on Windows 7 x64, but this issue has been present for a long time. When clicking a link that opens a new window (ie a link using target="_blank") the new window does not open maximized. For example on the page http://www.protodave.com/tools/verifying-a-dkim-txt-record-and-key-length/ when you click the 'DKIM Key Checker' link it opens the target page in a new window. The window does not open maximized. I currently have Firefox customized with the Title Bar and Menu Bar showing and I do not have 'Open new windows in a new tab instead' checked. There is a workaround for this issue and that is to disable the Title Bar in the customize menu. When the Title Bar is not enabled then new windows properly open maximized. The fact that Firefox produces the expected behavior when in the default no-title-bar state and produces undesired behavior in the title-bar-enabled state leads me to believe this is either a bug or (hopefully) an obscure about:config option that I have so far been unable to descry. I prefer the Title Bar enabled and so I just live with the issue, but it is definitely aggravating. Please help.

გადაწყვეტა შერჩეულია

Shift+Click should open a window that is the same size of the window that the link was clicked in.

However in Windows, if you move the window to the top right, it will automatically maximize (something to consider as a work around in the meantime)

This issue is being tracked in bug 1005098, however there is no ETA when this will be worked on. It is considered for 38, but not implemented.

პასუხის ნახვა სრულად 👍 2

ყველა პასუხი (2)

შერჩეული გადაწყვეტა

Shift+Click should open a window that is the same size of the window that the link was clicked in.

However in Windows, if you move the window to the top right, it will automatically maximize (something to consider as a work around in the meantime)

This issue is being tracked in bug 1005098, however there is no ETA when this will be worked on. It is considered for 38, but not implemented.

Thank you. I did not think of Shift-Click as an optional workaround. Thank you also for providing the bug number. I will see if I can provide help with tracking when the bug was introduced.