Closed Bug 267857 Opened 20 years ago Closed 19 years ago

View thread mode in Google groups results in intermittently hosed web page

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: jgbishop, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041103 Firefox/1.0RC2

The provided URL (which is quite long), fails to render correctly inside both
Mozilla (1.7.3) and Firefox (1.0 RC2). The page looks fine in Internet Explorer 6.0.

The URL points to the threaded view of a newsgroup posting (found by doing a
groups search at Google). What's expected is a left frame containing the
threaded view of post headings, and a right frame, showing the contents of up to
10 of the posts. What Firefox / Mozilla actually render are two empty frames,
each of which takes up 50% of the page (width-wise).

Reproducible: Always
Steps to Reproduce:
1. Visit the provided URL
(http://groups.google.com/groups?hl=en&lr=lang_en&c2coff=1&threadm=FcS3a.2133%24bK4.339596%40ursa-nb00s0.nbnet.nb.ca&rnum=30&prev=/groups%3Fnum%3D50%26hl%3Den%26lr%3Dlang_en%26c2coff%3D1%26q%3Dhostforweb%26btnG%3DSearch).
2. Note the problem.
As Asa mentioned (http://weblogs.mozillazine.org/asa/archives/006789.html),
rendering needed further testing. Not sure if this falls under that category,
but that's why I placed the ? on the blocking flag. Besides, I'm not familiar
with this flag business anyways (so apologies for any mistake I've made).
Flags: blocking-aviary1.0?
I'm unable to reproduce with today's branch build on windows XP. If you can get
this narrowed down to a simplified testcase and you can find out when it
regressed, please re-nominate.
Flags: blocking-aviary1.0? → blocking-aviary1.0-
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.