And to point you at the parts of my scripts I suspect are exercising the bug: Essentially what is happening is that a setInterval from trajectory.js is doing object.image.width = new_width; object.image.height = new_style; at the same time as a setTimeout from drag.js is doing object.image.style.left = new_left; object.image.style.top = new_top; So the first thing I suggest looking at is the Mozilla code that implements those two actions. Is there any chance that they could step on each other?
I see this on Linux too.... computed style agrees with the visual display, and both disagree with the inline style. Haven't looked at the code yet... does it all use inline style? Or does it use any stylesheets and twiddle classes dynamically to make objects match various selectors?
OS: Mac System 9.x → All
Hardware: Macintosh → All
It uses inline style. I propose someone at least look into whether it's an easy fix by Mozilla 1.0.
So... I just revisited this intending to figure out what's going on, and I can no longer reproduce it (in a current trunk build). Bob, are you still seeing this?
Mass-reassigning bugs to email@example.com
Assignee: jst → dom_bugs
Bob, is this still a problem?
bz, closing based on your comment 4, as Bob's email address is dead and no response to comment 6. please adjust if I'm off base.
Assignee: general → nobody
Status: NEW → RESOLVED
Last Resolved: 10 years ago
QA Contact: ian → general
Resolution: --- → INCOMPLETE
Sounds about right.
You need to log in before you can comment on or make changes to this bug.