sizemode=maximized causes multiple resize events on startup

RESOLVED WONTFIX

Status

()

Core
Widget
RESOLVED WONTFIX
9 years ago
7 years ago

People

(Reporter: blassey, Unassigned)

Tracking

({mobile})

Trunk
mobile
Points:
---

Firefox Tracking Flags

(fennec2.0+)

Details

this is a follow up from bug 477653 which worked around the problem to ignore 1 of the 3 resize events that is sent to Fennec.  It would be great for all xul apps that want a maximized window (common on mobile platforms) to only get one resize event on start up.

quoting the description from bug 477653:

> when using sizemode=maximized in our window define, we see multiple resize
> events on linux and windows mobile.
> 
> http://mxr.mozilla.org/mobile-browser/source/chrome/content/browser.xul#55
> 
> However, when we use fixed sizes like 'width="720" height="420"', there is only
> resize event fired.
> 
> On linux:
> 
> without sizemode=maximized:
> resize: 720x420
> 
> with sizemode=maximized:
> resize: 1025x800
> resize: 1025x800
> resize: 720x420
> 
> This problem was uncovered when we switched from our browser window having a
> fixed size to just using the sizemode attribute in bug:
> 
> https://bugzilla.mozilla.org/show_bug.cgi?id=476705
tracking-fennec: --- → ?
(Reporter)

Updated

9 years ago
tracking-fennec: ? → 1.0b1-wm+

Comment 1

9 years ago
now we use fullscreen.  brad, do we continue to see these resize events?
(Reporter)

Updated

9 years ago
Assignee: nobody → bugmail
Status: NEW → ASSIGNED
with fullscreen I still get 3 resizes:

resize 1023x562
resize 480x640
resize 480x640
its not clear to me that this is a perf problem anymore, although its worth some investigation
Assignee: bugmail → nobody
This is a mass change. Every comment has "assigned-to-new" in it.

I didn't look through the bugs, so I'm sorry if I change a bug which shouldn't be changed. But I guess these bugs are just bugs that were once assigned and people forgot to change the Status back when unassigning.
Status: ASSIGNED → NEW
pushing this to 2.0+ to determine if this is actually a perf problem
tracking-fennec: 1.0b1-wm+ → 2.0+
best we can tell, this isn't a perf issue anymore
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.