41471 - [LAYER] scrollbars=no ignored in window.open in page with oversize layer

Status: VERIFIED FIXED

(Tech Evangelism Graveyard :: English US, defect, P3)

Description

[Malte Ubl]

Hi,

there are several other bugs filed about this matter but this might be a special 
case:

goto:
http://www.blackbomb.de and click on on of the images; it will open a new window 
which would perfectly fit the screen if there wouldnt be a horizontal scrollbar 
which shouldnt be there.

The special case is that this page contains a moving background in a CSS layer 
which is indeed bigger than the screen.

This doesnt work in both the M15 Milestone as well as the 06-04-00 Daily.

Comment 1

[Asa Dotzler [:asa]]

Sorry for the spam.  New QA Contact for Browser General.  Thanks for your help
Joseph (good luck with the new job) and welcome aboard Doron Rosenberg

Comment 2

[Blake Ross]

Well, initially I saw two issues here - one, when I tried to scroll to the 
right in the page that popped up, I got the worst possible kind of crash (I've 
never even encountered this before) - an actual vc++ runtime error regarding a 
pure virtual function call [vc++ runtime errors are worse than typical gpf's].  
I also did see that the page had a scrollbar and was way too wide.  

However, just as I was about to confirm this, I checked out the source and 
noticed that the entire document is based around and littered with layers.  We 
no longer support layers, and I'm not even going to try dissecting this to see 
if it's a layer problem or not.  I'm going to mark this as invalid...reporter, 
if you're able to make a testcase of this that still displays the same buggy 
behavior but doesn't use any layers, feel free to comment here and I'll reopen.

Comment 3

[Malte Ubl]

Uhmm,

please define Layer:
do you mean <layer ....></layer>
Probably not, cuz there are none.

If you are talking about <div style="position:abolute; ...> and you are not 
supporting that, than you are gonna be in big trouble because the most popular, 
and probably best WYSIWYG Editor "Macromedia Dreamweaver" in its Version 2.0 (I 
dont know about 3.0) is generating exactly that code. All crucial parts of the 
page are generated, only one rather unimportant JavaScript function "handmade".

If you talk about the method of accessing the layer through document.layer using 
a test based on whether we have a navigator version greater or equal to 2 than 
you're probably right and the JavaScript code is buggy.

Anyway,
my browser never crashed and I think tha if I tell a window that its not 
supposed to have a scrollbar than it simply shouldnt have one, even if it 
contains buggy JavaScript.

Comment 4

[Blake Ross]

I was referring to the overabundant use of document.layer and other such dom 
methods throughout the document.  I'd give you more specific examples, however, 
as of now this bug remains invalid since I'm no longer able to access the URL.

Comment 5

[Malte Ubl]

Server's up again.

I know how to work around the problem document.layer problem but I guess I'll 
just buy Dreamweaver 3 and hope that it'll make better code. I think I once read 
you would still support document.layer for backward compatability but that must 
be outdated.

Sorry for taking up your time. Keep up the good work.

Comment 6

[Doron Rosenberg (IBM)]

verified layer use. 

Comment 7

[ekrock's old account (dead)]

Moving all [LAYER] bugs to Evangelism component for tracking and open-source
evangelism by mozilla community members of sites that need to upgrade to support 
web standards such as HTML 4.0 (instead of LAYER/ILAYER) and the W3C DOM
(instead of Nav4 document.layers[] or IE document.all()). Sites should be
lobbied to do the upgrade using the email templates that are linked to from
http://www.mozilla.org/newlayout/bugathon.html#layerbugs . When a site's owner
has confirmed receipt of the message requesting an upgrade, the bug should be
marked with the keyword evangelized to indicate that evangelism for that bug is
complete. When the site finishes the upgrade and supports standards, the bug
should be closed.

Comment 8

[Blake Ross]

Dawn, just thought this UNCONFIRMED/INVALID state was pretty interesting...

Comment 9

[ekrock's old account (dead)]

Reopening to register fact that this page probably isn't yet upgraded (until it 
is, at which point we'll close the bug). evangwanted. Clearing cc:s as a 
courtesy to reduce spam.

Comment 10

[Zach Lipton [:zach]]

SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for 
this component.

Sorry about the spam

zach

Comment 11

[Blake Ross]

Reassigning Evangelism bugs to me, the component's new owner.  I would like to 
take this opportunity to thank [e-mail] for all of his dedication, 
contributions, and hard work, and wish him luck at his new job.  Thanks, nobody.

Comment 12

[Blake Ross]

Mass confirming Evangelism bugs to get off the Unconfirmed radar

Comment 13

[Blake Ross]

-> [e-mail] for my evangelism bugs.

removing the now-depreciated evangelism-related keywords.

setting platform to All.

Comment 14

[Andreas M. "Clarence" Schneider]

Works for me.

Comment 15

[Blake Ross]

Reassigning evangelism bugs to [e-mail].

Comment 16

[Bob Clary [:bc] (inactive)]

This site uses older Dreamweaver code but does not throw any layer related
errors after visiting several pages although it does throw some errors related
to missing MM_ functions.

The opened windows appear without scroll bars for me.

Marking fixed and updating to be tracked as a Dreamweaver related site.

Comment 17

[Bob Clary [:bc] (inactive)]

All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
details.

Comment 18

[Kai Lahmann (is there, where MNG is)]

no problem left there