Closed
Bug 290970
Opened 20 years ago
Closed 20 years ago
Javascript event causes flicker of overflow:auto DIV
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 132337
People
(Reporter: bugzilla, Assigned: bugzilla)
Details
(Keywords: testcase)
Attachments
(1 file)
|
1.00 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
A certain combination of DIVs and javascript events causes an unpleasant
flickering effect. See 'steps to reproduce' for details.
Reproducible: Always
Steps to Reproduce:
The setup:
- two DIVs are set to float:left such that they are positioned side-by side.
- In the right-hand DIV is a further nested DIV set to overflow:auto
- In the right-hand DIV is a further DIV whose content is updated by a
javascript event (eg. onKeyUp in a text field)
Actual Results:
When the event is fired, the div with overflow:auto appears to 'jump' briefly to
the left (and up, depending on its position). Repeated event calls cause an
unpleasant flickering effect.
Expected Results:
The DIV should not appear to move.
I found the same results in Mozilla 1.6 (WinXP)
I just tried taking out the first left-aligned DIV ( the red DIV in the test
case ) and the flickering still occurs. So all that's required is one
left-aligned DIV with a nested overflow:auto DIV.
Comment 3•20 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b2) Gecko/20050419
Firefox/1.0+
WFM. Reporter, can you please try with the latest nightly (1.1beta) build and
see if this is still an issue for you? Thanks!
http://ftp.uni-erlangen.de/pub/mozilla.org/firefox/nightly/latest-trunk/
Comment 4•20 years ago
|
||
Please test with trunk builds before filing layout issues, thanks.
*** This bug has been marked as a duplicate of 132337 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
This does appear to have been fixed in the latest build. Apologies for my lack
of familiarity with procedure :)
Comment 6•20 years ago
|
||
No problem, thanks for taking the time to file a bug
You need to log in
before you can comment on or make changes to this bug.
Description
•