Closed
Bug 578677
Opened 15 years ago
Closed 15 years ago
Firebug panel is not properly repainted when scrolled
Categories
(Core :: Web Painting, defect)
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| blocking2.0 | --- | betaN+ |
People
(Reporter: Honza, Unassigned)
Details
(Keywords: regression, Whiteboard: [firebug-p1])
Firebug's panel content is not repainted correctly. Only top and bottom areas of the window (height varies on how quickly you move the scroll bar thumb) are repainted.
Reproducible configuration:
- Firebug 1.6a16
- Firefox 4.0b1
It seems to be win specific problem as it works on mac (not sure about other platforms).
All works in Fx 3.6
| Reporter | ||
Updated•15 years ago
|
Whiteboard: [firebug-p1]
| Reporter | ||
Comment 1•15 years ago
|
||
Here is where you can download Firebug:
http://getfirebug.com/releases/firebug/1.6X/
Honza
Comment 2•15 years ago
|
||
What's the regression range?
Updated•15 years ago
|
Keywords: regressionwindow-wanted
| Reporter | ||
Comment 3•15 years ago
|
||
I don't see the problem in:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a5pre) Gecko/20100701 Minefield/3.7a5pre
But I see it in 4.0b1:
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:2.0b1) Gecko/20100630 Firefox/4.0b1
Honza
| Reporter | ||
Comment 4•15 years ago
|
||
Just for future reference, here is a thread reporting the same problem:
http://groups.google.com/group/firebug/browse_thread/thread/eb5d998edd1ec176
Honza
Comment 5•15 years ago
|
||
Comment 3 doesn't make sense to me. You see the problem in an _older_ build but not in a _newer_ one? Is the problem still there on mozilla-central tip right now?
Comment 6•15 years ago
|
||
3.7a5pre = no problem
4.0b1 = problem
| Reporter | ||
Comment 7•15 years ago
|
||
I have just updated to:
Mozilla/5.0 (Windows; Windows NT 6.0; en-US; rv:2.0b2pre) Gecko/20100715 Minefield/4.0b2pre
and the problem is clearly there.
Looks like broken only in 2.* builds.
Honza
Comment 8•15 years ago
|
||
I think we're having a serious communication problem here.
Can you tell me the two mozilla-central nightlies (and specifically the revisions they were built from) that bracket when the problem appeared? Testing releases of various sorts is not useful for that.
Comment 9•15 years ago
|
||
And UA strings are totally useless for identifying builds, by the way...
| Reporter | ||
Comment 10•15 years ago
|
||
Not sure how to effectively find the regression range. The test requires installing Firefox creating a profile, installing Firebug and executing some steps to see the problem.
I have been using builds from here:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/
Also how can I find the revision if it isn't in the UA string?
Any tips how to do that and don’t spend a week on it?
Honza
Comment 11•15 years ago
|
||
> I have been using builds from here:
That's the right place, if you use the mozilla-central subdirs. Just using those builds and finding the one right before the behavior change and the one right after using binary search should work, right?
You can get the useful revision id from about:buildconfig.
Comment 12•15 years ago
|
||
Note that since you have this down to less than a month, binary search would require 5 builds or less to be tested...
| Reporter | ||
Comment 13•15 years ago
|
||
My testing shows that the problem appeared between:
http://hg.mozilla.org/mozilla-central/rev/6b36b6da79bd
and
http://hg.mozilla.org/mozilla-central/rev/9c85f9aaec8c
Which corresponds to:
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2010-06-27-03-mozilla-central/
and
http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2010-06-28-03-mozilla-central/
Honza
Comment 14•15 years ago
|
||
OK, so http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6b36b6da79bd&tochange=9c85f9aaec8c
There are various things in there that might be relevant, including bug 573931, bug 572612. Hard to tell more than that given the complete lack of steps to reproduce in this bug....
blocking2.0: --- → ?
Keywords: regressionwindow-wanted → regression
| Reporter | ||
Comment 15•15 years ago
|
||
1) Install Firebug (the current latest is 1.6a17, http://getfirebug.com/releases/firebug/1.6X/)
2) Load www.google.com
3) Open Firebug UI and switch to the DOM panel
4) Use scrollbar-thumb to vertically scroll the panel content.
5) The panel content must properly scrolled and painted.
BUG: The content is not properly repainted.
See attached screenshot here:
http://groups.google.com/group/firebug/browse_thread/thread/eb5d998edd1ec176
This Firefox revision can be used to reproduce the problem:
http://hg.mozilla.org/mozilla-central/rev/9c85f9aaec8c
Honza
Comment 16•15 years ago
|
||
I assume that's not a xul tree, right?
Comment 17•15 years ago
|
||
(In reply to comment #16)
> I assume that's not a xul tree, right?
no, they're all <browser>s (inside a <deck>), iirc.
Retest with latest trunk to see if this is fixed with retained layers...
| Reporter | ||
Comment 19•15 years ago
|
||
I tested with latest-mozilla-central built from http://hg.mozilla.org/mozilla-central/rev/5fda39cd703c (4.0b2pre)
The STR from comment #15 works now, but there is yet another case where the problem can be reproduced.
1) Install Firebug with debug-tracing enabled (the current latest is 1.6a17,
http://getfirebug.com/releases/firebug/1.6X/)
2) Load www.google.com
3) Open Firebug tracing console (Firebug menu -> Open Firebug Tracing)
4) Check ACTIVITYOBSERVER option on the tracing console (just to have some logs so the content can be scrolled).
5) Reload the page (you can reload more times to have more logs)
6) Use vertical scroll-thumb to scroll content of the window -> not properly repainted.
(In reply to comment #17)
> (In reply to comment #16)
> > I assume that's not a xul tree, right?
>
> no, they're all <browser>s (inside a <deck>), iirc.
correct
Honza
blocking2.0: ? → betaN+
| Reporter | ||
Comment 20•15 years ago
|
||
I am not seeing the problem (mentioned in comment #19) in 4.0b4pre anymore.
Honza
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•7 years ago
|
Component: Layout: View Rendering → Layout: Web Painting
You need to log in
before you can comment on or make changes to this bug.
Description
•