Closed Bug 472545 Opened 16 years ago Closed 4 years ago

mochitest/chrome has a failure when we navigate back to a page and the vertical scroll bar cannot be >450

Categories

(Core :: DOM: Navigation, defect)

ARM
Maemo
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE

People

(Reporter: jmaher, Unassigned)

References

Details

in the chrome://mochikit/content/chrome/docshell/test/chrome/test_bug215405.xul, we scroll the x, y scroll axis to the maximum allowed, then navigate away from the page and back to it.  When we come back, the X scroll bar is correct, but the Y scroll bar is always at 450.  The problem is the test determines the maximum scroll for Y axis is 510.

This works on desktop fennec, just fails on maemo.  It passes if I originally scroll to 450 (instead of the calculated max) and fails at 451.
Blocks: 473562
moving to proper component
Component: General → Document Navigation
Product: Fennec → Core
QA Contact: general → docshell
Where is the 450 number coming from, exactly?
I found the 450 number by trial and error.  I kept adjusting the value of
height in:
http://mxr.mozilla.org/mozilla-central/source/docshell/test/chrome/test_bug215405.xul#37

until I found out that anything >450 would fail.

I realized this might be related to bug 483336
Hmm.  You mean 450 is the size you need to pass to window.open to be able to pass the test?  How big is your screen, if I might ask?  What's the size of the window that actually gets opened?
correct on the 450 is the size needed to pass the test.  I honestly don't know the resolution (I think it is in the range of 600 x 400).  Let me see if somebody else from Mobile (gavin) can get the exact dimensions. 

I do know that for wince we are on a 320x200'ish screen size, so this test might react differently then.
I'm pretty sure we don't allow window sizes larger than the screen.. or at least I seem to recall so.  Can you get this to fail on desktop by jacking up the size of that window to larger than your desktop screen resolution?

fwiw, looks like the n810 has an 800x480 screen; if your chrome is about 30px, then the 450px number would be the max size your content window could get.
I tried playing with this on fennec for the desktop and used a height of up to 16000 and this always passed.  The more I think about it this is really related to bug 483336 or bug 476703.

I am open to trying out anything else.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.