after new install browser window should conform to 800x600

RESOLVED EXPIRED

Status

SeaMonkey
UI Design
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: marlon bishop, Assigned: jag (Peter Annema))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
According to marketing indications most sites are developed for 800x600, since
that's where large majority of screen sizes are at right now. We need to start
the browser for the first time with a larger window size that acommodates this

Comment 1

16 years ago
This is a one-line fix to navigator.xul, v1.374, line 53 I believe:
-         width="610" height="450"
+         width="800" height="600"

Evelyn, 
Do you want to nominate this?

Comment 2

16 years ago
1. those dimensions are absolutely wrong for the same reason that the current 
dimensions are not 640x480.

2. please don't do this.

3. please find a better way to do this, we should be able to have no dimensions 
and let the os pick a window size for us.

Comment 3

16 years ago
Back to Marlon (and mktg) to spec out what engineering should implement.
Assignee: sgehani → marlon

Comment 4

16 years ago
ccing Greggl
Product: Core → Mozilla Application Suite
Assignee: marlon.bishop → jag
QA Contact: pawyskoczka

Comment 5

9 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED

Comment 6

8 years ago
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.