Closed
Bug 53972
Opened 24 years ago
Closed 24 years ago
canvas background fixup causes weird incremental repaint
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Core
CSS Parsing and Computation
Tracking
()
RESOLVED
WORKSFORME
M18
People
(Reporter: dbaron, Assigned: attinasi)
References
()
Details
(Keywords: css1, regression)
Something related to the canvas background fixup or body fixup rule is working strangely in some cases. STEPS TO REPRODUCE * load http://www.people.fas.harvard.edu/~dbaron/css/test/implied ACTUAL RESULTS: * **some of the time**, the correct display (dark green around edges) flashes, but is then replaced by light green where the dark green should be. Sometimes it works correctly. It becomes correct again after an expose event. EXPECTED RESULTS: * Light green BODY, dark green HTML (in margins of BODY and below bottom of BODY) BUGGY IN: * MacOS 9.0.4 Mozilla 2000-09-22-20
Assignee | ||
Comment 1•24 years ago
|
||
This sounds like it could be a mac-specific rendering issue (I cannot see it on NT or Linux, and David did report it as a mac-only bug). Reassigning to rendeing team to investigate.
Assignee: attinasi → kmcclusk
Assignee | ||
Comment 2•24 years ago
|
||
NOTE: I just saw this on WinNT - it is really strange because I exposed the window which was partially obscured by my mail window, and the outter are was mostly light green (the newly exposed part anyway) and then I hid it again and re-exposed it an it repainted correctly. Also, if you resize it after the initial exposure it updates correctly. I believe the problem is in the html.css file, the rule: :viewport, :viewport-scroll, :canvas { display: block; background-color: inherit; } is causing the problem. If yuo remove 'background-color: inherit' it works fine. I believe that this is a problem with the style resolution battling with the body fixup rule. Taking back now...
Assignee: kmcclusk → attinasi
Assignee | ||
Comment 3•24 years ago
|
||
Accepting and updating the platform fields, adding regression kwd.
Status: NEW → ASSIGNED
Keywords: regression
OS: Mac System 9.0 → All
Priority: P3 → P2
Hardware: Macintosh → All
Target Milestone: --- → M18
Assignee | ||
Comment 4•24 years ago
|
||
OK, after another 15 minutes of playing with this it is clear that those rules are NOT the problem. This bug is just tempermental and I was not being thorough enough. Please disregard my prior comment (2000-09-25 10:56).
Comment 5•24 years ago
|
||
FWIW, without those rules it stops using the default background colours. Hey, if these non-standard extensions were documented somewhere, I could have been more sure of what I was doing when I edited the rules with those strange and interesting pseudo-classes, ok... ;-)
Assignee | ||
Comment 6•24 years ago
|
||
David, do you have any idea when this started happening? I cannot seem to repro it in a build from 9/19, but easily can from a build of 9/22 (as you reported it). Have you seen this before 9/22?
Reporter | ||
Comment 7•24 years ago
|
||
I reported it the first time I saw it, but I didn't test that page for months before I saw it.
Assignee | ||
Comment 8•24 years ago
|
||
Nominating for RTM since this is really ugly and will probably show up on the BoxAcidTest as well.
Keywords: rtm
Assignee | ||
Comment 9•24 years ago
|
||
Popping up a content-menu over the HTML are and dismissing by clicking in the BODY will reporduce this problem quite reliably. Covering and exposing the window will also reporduce it, but much less reliably.
*** Bug 54660 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 11•24 years ago
|
||
CC'ing Kevin to check out. Thanks, Kevin.
Comment 12•24 years ago
|
||
CCd myself because the rule above and the origin of the canvas background are of interest to me (bug 19329).
Comment 13•24 years ago
|
||
It's been said that this *may* show up on the Box Acid Test. Can anyone confirm this?
Assignee | ||
Comment 14•24 years ago
|
||
I cannot check the Box Avid Test because verso.style.com is down right now. I'll keep trying.
Assignee | ||
Comment 15•24 years ago
|
||
Actually, I cannot reproduce this at all anymore. I tested David and Ian's pages: http://www.people.fas.harvard.edu/~dbaron/css/test/implied http://www.bath.ac.uk/%7Epy8ieh/internet/eviltests/htmlbodyrendering6.html and a modified Box Acid Test page (since the original is down) at: http://pessoal.mandic.com.br/~aristeu/boxacidtestIE5corrected/IE5-acidtest.htm using the context-menu technique and the random hide/show window technique and I cannot get the bug to show. Marking WORKSFORME - please reopen if you can still reproduce it. (I'll also check the Box Acid Test when it is up again.)
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 16•24 years ago
|
||
I couldn't reproduce this yesterday either, but did not check this thoroughly. I wouldn't say it was stop ship, even if it did affect the box acid test. This is (was) a very minor bug IMHO. BTW, Marc: the box acid test is at: http://style.metrius.com/boxacidtest/
Comment 17•24 years ago
|
||
Netscape's standard compliance QA team reorganised itself once again, so taking remaining non-tables style bugs. Sorry about the spam. I tried to get this done directly at the database level, but apparently that is "not easy because of the shadow db", "plus it screws up the audit trail", so no can do...
QA Contact: chrisd → ian
Comment 18•23 years ago
|
||
Reassigning QA to reporter. I could never reproduce this much on the given pages anyway, so I couldn't really verify it.
QA Contact: ian → dbaron
You need to log in
before you can comment on or make changes to this bug.
Description
•