Closed
Bug 914864
Opened 12 years ago
Closed 12 years ago
Unexpected frame dimensions
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: botond, Assigned: botond)
Details
STR: Open http://people.mozilla.org/~kgupta/grid.html in the B2G browser with latest m-c.
The dimensions of the root scroll frame on this page are 19200 x 136943 app units, or 320 x 2282 CSS pixels, on my device. 320 pixels is the width of the screen (the content is wider than that), and 2282 pixels appears to be the height of the content (the screen is shorter than that).
I think it's unexpected that the frame's size derives one of its dimensions from the screen size and the other from the content size.
![]() |
||
Comment 1•12 years ago
|
||
Can you please attach the frame dump you're looking at?
Assignee | ||
Comment 2•12 years ago
|
||
(In reply to Boris Zbarsky [:bz] from comment #1)
> Can you please attach the frame dump you're looking at?
I got these figures by putting a print statement in RecordFrameMetrics(), where FrameMetrics::mCompositionBounds is set based on the scroll frame's size.
How do I get a frame dump?
![]() |
||
Comment 3•12 years ago
|
||
nsIFrame::List() on the viewport frame.
Assignee | ||
Comment 4•12 years ago
|
||
Well it took a while to figure out how to get this information on b2g (I ended up opening a file and writing to it), but here's the output of nsIFrame::List() on aScrollFrame in the offending RecordFrameMetrics call: http://pastebin.mozilla.org/3029002 (it's long because there is a large table in the document).
Does that help?
![]() |
||
Comment 5•12 years ago
|
||
Hmm. Yeah, that's odd. The root scrollframe size should be based on the viewport size in both dimensions; that's what I see on desktop. But that's certainly not what the frame dump shows...
Comment 6•12 years ago
|
||
Could have something to do with the viewport being overridden (mViewportOverridden, ResizeReflow in nsPresShell.cpp).
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → botond
Assignee | ||
Comment 7•12 years ago
|
||
I'll take a look at this because it's blocking my work on bug 935219.
Assignee | ||
Comment 8•12 years ago
|
||
Can't seem to reproduce this issue any more. Maybe something got fixed in layout that made this problem go away?
Assignee | ||
Comment 9•12 years ago
|
||
Closing as I don't see this anymore. Will reopen if I see it again.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•