Closed Bug 26285 Opened 25 years ago Closed 25 years ago

Commercial tree UI doesn't render

Categories

(Core :: DOM: UI Events & Focus Handling, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: slogan, Assigned: mikepinkerton)

Details

(Keywords: platform-parity, Whiteboard: [PDT-])

I started seeing this on a commercial pull 2/1/00, previously I was seeing no 
problems with a build 4 or 5 days prior, with the same OS and such.

I start commercial, and more often than not, I come up with a blank window. If I 
move the mouse, sometimes things draw, but on partially. Often, clicking on a 
menu bar the menu doesn't display. This happens 40 - 50% of the time. Sometimes, 
moving the mouse never helps, this tells me that events aren't being seen.

I tried turning off gfx scrollbars, this had no bearing.

My guess is we have a big timing/plumbing issue that is caused by the extra time 
it takes for the IM component and all of its libs to load. The problem seems to 
be that someone isn't seeing the events they need to see to draw the UI.

RedHat 6.0, Gtk+ 1.2.1.
Another data point: if the UI comes up ok on startup, I *never* see UI failure 
of any kind. However, if it starts up bad, I frequently can't recover and have 
to ctrl-C to kill it. So, the problem exists at startup.
Another thing to node is that optimize build does not have this problem. So this
leads me to believe that it is a timing issue.
Status: NEW → ASSIGNED
I still see random occasional crashes on startup that happen for no apparent
reason.  It usually happens right after the bookmark messages pass by.
I did the commercial build on RH6.1 and gtk+ 1.26 and had similar problem, while
testing the build I realized that commerical build goes to home.netscape.com
instead of www.mozilla.org.

What did was to set the home page in commercial build to www.mozilla.org and I
did not have the problem with page not rendering.

Next I took the mozilla build and set the home page to home.netscape.com and
then the browser started to display gray pages.

This leads me to belive that it is a general rendering bug.
Sounds like 20185 to me.  What a bug, baby.
Adding [PP] to summary
Summary: [BETA1] Commercial tree UI doesn't render → [BETA1][PP] Commercial tree UI doesn't render
Due to Beta indication in Summary, putting beta1 into keyword field.
Keywords: beta1

*** This bug has been marked as a duplicate of 20185 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified duplicate
Status: RESOLVED → VERIFIED
I don't think this is a dup. This started happening just recently, long after
the duplicate bug was opened. Reopening, assigning to saari.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
Assign to saari
Assignee: waqar → saari
Status: REOPENED → NEW
Keywords: pp
Summary: [BETA1][PP] Commercial tree UI doesn't render → Commercial tree UI doesn't render
This is essential for beta; marking PDT+.
Whiteboard: [PDT+]
spam: adding self to cc list.
Peter, everyone, I'm way too doomed with focus to be looking at this.

*anyone* less doomed (except hyatt, he is in the same focus quagmire) would be a 
better choice to look at this.
Assignee: saari → trudelle
Sure sounds like something is not being initialized properly, rather than a 
logical problem with events. Since this does not occur in optimized builds, 
which is all we are shipping, and there is a simple workaround for debug builds 
(change the home page), I don't see how this is blocking any development work, 
nor why it is PDT+ for beta.  removing PDT+ for reconsideration.
reassigning to pinkerton as p3 for M14 (just so we don't lose track of it)
Assignee: trudelle → pinkerton
Whiteboard: [PDT+]
Target Milestone: M14
um, sure, i'll take this, but it won't get fixed for m14 for sure. pushing to 
m15.
Status: NEW → ASSIGNED
Target Milestone: M14 → M15
Whiteboard: [PDT-]
does anyone still see this? if not i'm marking it worksforme
after talking to syd, marking WORKSFORME.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → WORKSFORME
Keywords: verifyme
Verified per pinkerton's comments.
Status: RESOLVED → VERIFIED
Keywords: verifyme
Component: Event Handling → User events and focus handling
You need to log in before you can comment on or make changes to this bug.