Closed Bug 69286 Opened 24 years ago Closed 22 years ago

agdayta.com - Layered Page Rendered Improperly

Categories

(Tech Evangelism Graveyard :: English US, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: brian, Assigned: bc)

References

()

Details

(Whiteboard: [TOOL][DREAMWEAVER])

In the recent builds the main page at agdayta.com is being rendered improperly.
 I think it has something to do with the layers, but I'm not for sure.  I'm
afraid I'm not a good layer programmer. :)  Thanks!
Layers are not supported by Mozilla. Absolute positioning with CSS should be
used instead. Confirming and over to Evangelism (and default owner of Evangelism).

Brian, please read the Bug Reporting Guidelines at
http://www.mozilla.org/quality/bug-writing-guidelines.html and considers using
Bugzilla Helper at http://www.mozilla.org/quality/help/bugzilla-helper.html to
report bugs. Thanks for using Mozilla and reporting bugs!
Assignee: karnaze → evangelism
Status: UNCONFIRMED → NEW
Component: Layout → Evangelism
Ever confirmed: true
Forgot to update to default QA for Evangelism.
QA Contact: petersen → zach
I don't believe the page code was changed, but I believe this worked with
earlier Mozilla builds.  I'll have to downgrade to an older build and give it a try.
My fault.  It doesn't work in older builds either. :)  Sorry bout that.  I'll
have to have a little conversation with the page maker.  That's pathetic, using
layers on a content site selling services.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Brian, could we keep this open?  Mark it fixed once you have had that
conversation and the site has been fixed to use the W3C DOM and CSS?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
I just happened to load the page using Netscape 6, and everything was rendered
correctly.  Wonder where exactly in the line layer rendering quit working. 
Nominating mozilla0.9 & nsbeta1.
Keywords: mozilla0.9, nsbeta1
severity bump-up to major.  This worked in Netscape 6 so developers are writing
sites this way.  They will have to re-write sites to work with Netscape 6.5 or
7, and I don't believe this is our goal.
Severity: normal → major
update summary
Severity: major → critical
Summary: Page Rendered Improperly → Layered Page Rendered Improperly
is this really supported in Netscape 6.0 and not current builds? adding arun in
case he cares.
This is a Server side Browser detection problem.

If you look at the source when using a recent Mozilla build (2001042108/win2k)
for example, you will see HTML with layers, commented out javascript, etc. But
if you look at the source using NS6 you will see HTML without layers, with
javascript that uses getElementById and getElementsByTagName, etc.

So, the server is sniffing for Netscape6 and not Mozilla and is therefore
incorrectly serving up Navigator 4 HTML to Mozilla.
Reassigning evangelism bugs to bclary@netscape.com.
Assignee: evangelism → bclary
Status: REOPENED → NEW
sounds like this one has been resolved?
marking as resolved invalid.
Status: NEW → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → INVALID
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
Site no longer serves layers to Mozilla but is using dw 3 MM_findObj
Blocks: 51020
Severity: critical → minor
Status: RESOLVED → REOPENED
OS: Windows 98 → All
Hardware: PC → All
Resolution: INVALID → ---
Whiteboard: [TOOL][DREAMWEAVER]
Summary: Layered Page Rendered Improperly → agdayta.com - Layered Page Rendered Improperly
Why was this bug reopened ? Mozilla and IE render the site identically and there
is no real JS problem. The MM_findObj function defined in the header are not
used in the page. I think that the bug should be closed.
Works for me
Status: REOPENED → RESOLVED
Closed: 23 years ago22 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.