Closed Bug 37360 Opened 25 years ago Closed 25 years ago

Black areas appearing atop pages

Categories

(Core :: Layout, defect, P3)

Sun
Solaris
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: tor, Assigned: waqar)

References

()

Details

(Keywords: platform-parity, top100, Whiteboard: [nsbeta2+][dogfood-])

Attachments

(1 file)

Recently I've seen a number of pages which are showing black areas atop a normally rendered page. Generating expose events by dragging another window atop the content area shows that mozilla knows how to render these areas properly, it just draws black rectangles over the affected area. See the attached image for an example. Some other sites exhibiting the same problem: http://www.cinescape.com/ http://www.prodcat.panasonic.com/shop/product.asp?sku=PV-DC2090&CategoryID=293 Tested on a 4/26 CVS afternoon pull on solaris/native.
I see the same on linux 2000-042609 M16 And i believe this is recent regression and really bug 20185 - the only difference is that instead of grey it now paints black. I've encountered the "black" problem on all the sites that previously had the "grey" problem. The bug now triggers regardless of whether ViewManager2 is enabled or not.
Page displays fine on NT using latest build. I guess it must be Solaris (or Unix) specific
Assignee: troy → kmcclusk
This also occurs on (using Linux build 2000-04-27-09-M16): http://hotbot.lycos.com/ (previously http://www.hotbot.com/ , which I think is a top100 site) http://www.fas.harvard.edu/~dbaron/ viewer test4, test5, test8, test10, test13 Adding dogfood, nsbeta2, pp, and top100 keywords. I am seeing GDK assertions whenever I load pages that show this problem. For example: Gdk-CRITICAL **: file gdkregion.c: line 99 (gdk_region_get_clipbox): assertion `region != NULL' failed. Gdk-CRITICAL **: file gdkregion.c: line 291 (gdk_regions_subtract): assertion `source2 != NULL' failed. Gdk-CRITICAL **: file gdkregion.c: line 267 (gdk_regions_union): assertion `source1 != NULL' failed. cc:ing pavlov and blizzard I did not see this problem in a debug build I pulled during yesterday's (04-26 09:18 PDT) tree closure or a daily build from 4-25. (I've been seeing some milder messy painting problems for a few days longer, though.) Since it was reported above in a daily build from 04-26, could it be optimized/nondebug-only?
Keywords: dogfood, nsbeta2, pp, top100
it is hard to say... the assertions i'm sure are due to some changes I made last night. I will look at those, but they wouldn't be in the 4-26 build, so I think that is something else.
I was seeing these before the region changes pavlov made last night. The problem appears in both debug/non-opt and non-debug/opt builds pulled after the tree closed this morning (4/27). Tested on solaris/native with gtk+-1.2.7. I'm not seeing the gdk-critical messages that were mentioned by dbaron@fas.harvard.edu.
I have fixes for the region assertions. I don't know what is going on other than that though.
Putting on [dogfood-][nsbeta2+] radar.
Whiteboard: [nsbeta+][dogfood-]
Waqar can you take a look?
Assignee: kmcclusk → waqar
I'm not seeing the black areas on a 5/1 cvs pull on solaris/native. Looks like this may have been fixed already.
In the Linux nightly of 2000-05-02-08-M16, I'm still seeing this on http: //www.people.fas.harvard.edu/~dbaron/ , but not on the other pages.
And... in the same build, I'm seeing no painting in the borders of textareas (like the one I'm typing in now).
Accepting
Status: NEW → ASSIGNED
Target Milestone: --- → M17
Upating [nsbeta+] to read [nsbeta2+] in Status Whiteboard.
Whiteboard: [nsbeta+][dogfood-] → [nsbeta2+][dogfood-]
OK... the reason I was still seeing this is that my "Use viewmanager2" pref got turned off. I'm not sure how that happened (perhaps while testing this originally??). Is anyone else still seeing this bug with ViewManager2 turned on (the default)?
I'm not reproducing this problem with the June 2nd Linux build. ViewManager2 is turned on. David, Is this still working for you ?
Drew, Since this issue is not occuring for either David or myself, should we mark this as works for me ?
This was fixed with my checkin to widget/src/gtk/nsWindow.cpp on 5/15/2000.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This was fixed with blizzard's checkin.
Marking verified per last comments.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: