From initial top level screen, followed by sign-in, the top level redisplay leaves right 2/3 blanked



14 years ago
9 years ago


(Reporter: jgkneuer, Assigned: pavlov)



Firefox Tracking Flags

(Not tracked)





14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414

The top-level screen of has a left side array of labeled blue
buttons for user services, and the right side is filled with news, active
features (video, celebrities, ...).  The initial screen, invoked via
htpp:// displays fully.  If I login as a Comcast Subscriber (see
steps below), on return from login the top-level screen is blanked to neutral
grey for about the right 2/3 of its area.  It displays the blue buttons and, for
part of their widths, the page-top masthead and the features immediately to the
I can send a screen snapshot if desired.

Reproducible: Always

Steps to Reproduce:
2.Click sign-in
3.Enter ID and password and click sign-in
4.The screen redisplays partly blanked as in Details

Actual Results:  
Exactly as described in details.

Expected Results:  
It should have displayed the full top-level screen

This seems to have some relation to bugs 117475 and 140561.  The fix of clearing
the cache described there DOES NOT work.  The system is Suse Linux 9.3 with all
updates applied.  The machine is an older Dell XPS T500.

It is possible to cycle the back through the steps by:

Clicking on Mail in the masthead which opens the message center
1. Signing out
2. Clicking on Home (from "Home > Sign In" on the sign-in screen)
This returns you to the original fully displayed top-level screen.

Comment 1

14 years ago
Can you save the page with the problem and attach it here?  Use "Save as HTML"
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 14 years ago
Resolution: --- → EXPIRED


9 years ago
Component: Image: Painting → Image: Painting
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.