245247 - Forwarding NYTimes articles blocks left side of screen.

Status: RESOLVED EXPIRED

(Toolkit :: Form Manager, defect)

Description

[Harris Mirkin]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a1) Gecko/20040520
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a1) Gecko/20040520

When I attempt to forward an article from the NYTimes, and click in the
recipient's window to enter the name, the left fifth of the screen gets a gray
stripe that blocks the form (although I can type through the stripe without
seeing the form it I leave the cursor where it was). It also blocks when I try
and check how the article should be sent. It doesn't happen with the Washington
Post (whose form has the same general layout). I haven't tried it with other papers.

Reproducible: Always
Steps to Reproduce:
1.Click on an article name in NY times. It will take you to article.
2.Click on "email this article" and it will take you to form.
3.Click on recipients name box, or how to send article. Problem appears.

Actual Results:  
Gray stripe blocks left fifth of screen.

Expected Results:  
No gray stripe.

No special configuration was used. I'm using the latest version of Panther.

Comment 1

[Greg K.]

Site requires authentication. Harris, do you have a URL for an NYT article
demonstrating this problem that doesn't require registration?

Comment 2

[Bill Gillooly]

I have also been affected by the gray bar bug on the NY Times web-site.  It
happens to me exactly as first reported.  I have some additonal information that
may help:

When I was using Netscape 7.1 (Mac OS X 10.3.6), I never had this problem at
all.  For some reason, I forget why, I decided to check to see if there was a
newer version of Netscape available.  There was, I downloaded and installed
Netscape v7.2.  Since I'm a big NY Times on-line reader (and forwarder) it
didn't take long to see the problem.

After reading a review of Netscape 7.1 on the Macworld site, I decided to switch
to Mozilla.  I downloaded and installed v1.7.3 and still had the problem.

Your site nagged me that v1.7.3 was "more than 4 weeks old" and I still had the
problem so i downloaded and installed v1.8a4.  I've still got the problem AND
your site still nagged me that the release was more than 4 weeks old.

Comment 3

[Bill Gillooly]

Here's a URL as requested, but you may not be able to get in as you need to be a
registered user (it's free).

http://ea.nytimes.com/cgi-bin/email?REFURI=http://www.nytimes.com/2004/12/12/politics/12kerik.html&position=

All you need to do is go to the NYT web-site:  http://www.nytimes.com/

Select any article, click on the link on the right-hand side that says "E-Mail
This Article"  then enter an e-mail address.  When you start entering, you'll
get the gray bar.

Comment 4

[Gervase Markham [:gerv]]

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:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 5

[Gervase Markham [:gerv]]

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.