Browser viewing scope too small

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
10 years ago
8 years ago

People

(Reporter: Daniel Marschall, Unassigned)

Tracking

3.0 Branch
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2010-11-01], URL)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4

Please see "Steps to reproduce"

Reproducible: Always

Steps to Reproduce:
Steps to reproduce:

- Search in Google "wikipedia länder"
- Open website: www.fungeo.de/Wikipedia-Laender.html
- Your browser window resizes because of a JavaScript
- Maximize your Firefox window
- Go back to Google by clicking "back"
- The window is still maximized, but the "frame" (the scope of viewing) is still small from the other website!

Actual Results:  
Please see "Steps to reproduce"

Expected Results:  
Please see "Steps to reproduce"
(Reporter)

Comment 2

10 years ago
Please concentrate to the bug instead.

These fields are ****.
"Overview" See title line which descripes...
"What happens?" I descriped it...
"What did I expect?" That is doesn't happen...

I do know how to write a bug reports, but not with this interface that forces me things to write which I already wrote.

Comment 3

10 years ago
The Link I gave in comment #1 shows you how to write a proper bug report. It also shows how to find out if an extension is causing it. The bmo interface is simply trying to get all the info we need. 

It seems like you are in the wrong place.  this is not a support forum, but a technical bug reporting database for the developers. You can find end-user support at http://support.mozilla.com.
Version: unspecified → 3.0 Branch
(Reporter)

Comment 4

10 years ago
Sir, it is a bug in 3.0.4. If the window is maximied and the scope of viwing just little, it is a bug, not a technical problem that only I have. The only extensions I have is Google Toolbar (deactivated) and Tab Mix Plus.

Comment 5

10 years ago
Please follow the steps found at the link (the main is a new profile). Then report back with your results.
This is because you allow the website to resize your window (in Tools > Options > Content > Advanced JavaScript settings). You can't expect the next (or previous) website to "un-resize" your window.
(Reporter)

Comment 7

10 years ago
I deactivated all add-ons (that means Tab Mix Plus), restarted, also started in safe mode, bug is also there. And I will not clean reinstall my FF since I work with that machine and have all my data there. But I could test it at university. I could make screenshots of that issue, but there is not way to upload. For me it is clear that this is a bug because the size of the page-render does not increase when I maximize the window, until I reload.

@Ria Klaassen: I said, I maximated the window, but the page doesn't maximate. That means, the "Render" of the page is still small, when I maximate the window. When I go back with the back button, then Google is only ~ 200 pixel width but the window is big.

Comment 8

10 years ago
I am not sure what you are meaning either. My window does resize, but you said in steps to repro:
>- Your browser window resizes because of a JavaScript
>- Maximize your Firefox window
>- Go back to Google by clicking "back"
I resize, and my google window is perfectly fine. I can see. Now, without manually resizing, it happens as Ria said above, the window stays how it was.

Comment 9

10 years ago
By creating a new profile, it will keep everything on your old one (bookmakrs, etc), and you can delete it when done. You can upload at the top of the comments section of this bug report.
Yeah ok, now I see what the reporter means. This is a duplicate.
Whiteboard: [DUPEME]
(Reporter)

Comment 11

10 years ago
Did I wrote such an incomprehensible English when I listed the repro steps?

I just had taken some screenshots to show the problem directly

A: http://img216.imageshack.us/img216/7279/79470101ka4.jpg
B: http://img505.imageshack.us/img505/9056/80755786pp0.jpg
C: http://img505.imageshack.us/img505/1265/10328711lh7.jpg
D: http://img179.imageshack.us/img179/6320/46005833hv6.jpg
No, you did it correct, Daniel, sorry. I was not yet able to find the bug but it should exist.
It is most likely a bfcache bug. If you set browser.sessionhistory.max_total_viewers to 0 in about:config the bug shouldn't happen anymore. http://kb.mozillazine.org/About:config
(Reporter)

Comment 14

10 years ago
But that's not an excuse for the bug, is it? browser.sessionhistory.max_total_viewers has -1 at my machine. I never changed the value.
No, it is the result of the back-forward cache, new in Bug 274784. With 0 you switch it off and reverts to the old cache. Bug 404075 seems a similar bug but there should also be older ones.
This is a mass search for Firefox General bugs filed against version 3.0 that are UNCO and have not been changed for 200 days.

Reporter, please update to Firefox 3.6.10 or alter. Firefox 3.0 is no longer supported and is no longer receiving updates. After you update, please create a fresh profile, http://support.mozilla.com/kb/managing+profiles, and test to see if your bug still exists. If you still the bug, then please post a comment with the version you tested against, and the problem. If the issue is no longer there, please set the RESOLUTION to  RESOLVED, WORKSFORME.
Whiteboard: [DUPEME] → [CLOSEME 2010-11-01]
No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.