28351 - @home www page, WILL LOAD BUT NO INTERFACE OR GFX

Status: VERIFIED INVALID

(SeaMonkey :: General, defect, P3)

Description

[Lars Elias]

The page most @home users find when typing www into their browsers link field,
will not load. The page is 100% java, and none of it loads. The browser doesn't
crash however the page is reported as laoded, when, in actuality it has not even
begun to load.
I am using M13 build 2000012520 of Sea Monkey

Comment 1

[Richard Zach]

Thanks for reporting this.
1. The problem may already be fixed.  Could you try it with a newer build?
2. Can you give an URL which is reachable from outside @home which exhibits this
problem?
3. Failing that, could you save the page (File | Save as in Netscape 4.7 or IE)
and attach it ("Create an attachment" link) to this bug report?

Without being able to see the page, we won't be able to confirm the problem or
figure out what the problem is.

I checked www.home.com, www.home.net, and work.home.com on Linux build
2000.02.17.15, and they all looked fine.  If you see the same problem you see on
the page you were speaking of on one of these with the M13 build, then it's
likely that the problem has since gone away.

Comment 2

[Gervase Markham [:gerv]]

Zach - he says the page is 100% Java. As randomly downloaded nightly builds 
don't support Java (as far as I am aware) then the "nothing" he's seeing should 
be absolutely right...

Gerv

Comment 3

[Richard Zach]

Yes, but somehow I don't believe that @home has a "100% Java" homepage.  It
should just be a modified version of Excite, shouldn't it? cookefam, can you
clarify?

Comment 4

[Gervase Markham [:gerv]]

I've sent a reminder to the submitter to come and clarify the situation.

Gerv

Comment 5

[Gervase Markham [:gerv]]

Submitter sent me the following e-mail:

"here is the source file for the page. All these files make up the page, I
believe its laid out with frames, but could possibly be tables. I couldn't
get the index src for some reason sorry."

The four files attached are in the .zip I'm about to upload. They are far too 
weird for me to work out - can someone else have a look and see if we've got all 
the pieces of this jigsaw? If not, this'll have to be INVALID :-(

Gerv

Comment 6

[Gervase Markham [:gerv]]

Attachment: Files from submitter of bug

Comment 7

[Gervase Markham [:gerv]]

It's a zipfile, BTW. I haven't worked out this enter-mime-types gig yet, I don't 
think.

Gerv

Comment 8

[Sebastian Späth]

I had a look at the attachment, the zip contains 4 html files. They maybe part
of a frame containing webpage (most likely www.bayinsider.com), but the "parent
page" is missing.

chrome.html and upperhomeleft.html are containing Layers which Mozilla doesn't
support, that's why they are not working.

NS 4X doesn't show more than one textfield or broken images. I couldn't test the
JavaScripts there either with Mozilla or Netscape as they mostly do
document.writes to show (local) images, so I suggest to mark this bug INVALID.
But I'll leave that up to Christine as she owns the bug.

Comment 9

[Richard Zach]

I got someone with @home to let me look at the page.  The entire content of the
frame which didn't display for cookefam is inside <LAYER> tags.  So this is
INVALID, as gervase remarked.

@home has their own branded browser, and since the pages use proprietary
Netscape tags, I'm assuming it's a NS derivative.  CC ekrock to make sure that
if this is so, Excite@Home is aware of this and will change their content to
eventually work with Mozilla.

Comment 10

[Richard Zach]

I checked, they actually have customized vesions of both IE and NS, and do some
browser sniffing in the frameset page.  The IE-pages seem to get by with CSS, so
if they's make sure isIE4 is true when browsing with Mozilla, it would probably
work.

Comment 11

[Asa Dotzler [:asa]]

Verifying invalid.  

Comment 12

[Asa Dotzler [:asa]]

*** Bug 31216 has been marked as a duplicate of this bug. ***