Frame border color/dragging incorrect




Layout: HTML Frames
13 years ago
13 years ago


(Reporter: Csaba Gabor, Unassigned)


({helpwanted, testcase})

Windows XP
helpwanted, testcase

Firefox Tracking Flags

(Not tracked)




(2 attachments)



13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

This is a two part bug, but I am loathe to split it up because they are related.

The motivation for this example is to have background image (the canvas) in the
top level document with a resizeable easel in the top left corner.  Indeed, the
first sample code shows that this works pretty well on my IE 6 (one might take
issue with the fact that setting frameBorder="1" within the top left <FRAME>
should take the border sizes from the containing FRAMESETs' border attribute (or
that the FRAME should have a way of specifying it), but that is not our issue
here).  This also works if that same <FRAME frameBorder="1" ... > has that
frameBorder attribute set to 0 (only then there isn't the internal border).

Bug 1: What happens with Firefox is that the top left frame has no inner border,
and MORE IMPORTANTLY the top left frame is not resizeable in either direction.

Side note: I could imagine you (although I hope you don't) argue that Firefox
isn't obliged to do resizing if there is no border showing (which is why this is
a double bug report).  Indeed, in the example above with IE, if you go to where
you can't see the border between the bottom and right frames, you'll see the
mouse cursor change and allow a resizing drag.  Looks funny, but I'd far rather
have that than not be able to do the resizing at all.

So this brings us to the coloring issue.  I'm going to change IFrame.htm so that
there are some nice thick borders so that we can see what happens with colors. 
The outer frameset gets red, the inner one gets blue, and the top left one gets

Bug 2A)  Whoops, it looks like that green overrides the red and blue and ALL THE
FRAMES wind up with a green border.  If the second FRAME gets the
borderColor=green INSTEAD OF the first one, then it is ignored and every frame
winds up with a BLUE border.

Bug 2B)  If I set border=1 on the FRAMESETS then the color shown is black (and
not any of red, blue, or green).  Actually, this variant would be an acceptable
solution to the motivating problem except for the artifact of the 1px line
between FRAMEs two and three.

Bug 2C)  But more importantly, I'd like to be able to turn a border off for a
given frame using <FRAME frameBorder="0" ...>.  I assume the way this would work
is that if two abutting frames' borders are both turned off then there would be
no visible border separating them (hence not resizeable along that border if Bug
1 is not a bug), but if either of their borders is turned on then there is a
visible border between them, hence draggable.

Csaba Gabor from Vienna

Reproducible: Always

Steps to Reproduce:
1.  Put Main.htm and IFrame.htm in the same directory.  You'll need to supply an
image.jpg file in the same directory.  Then open Main.htm

  <META content="text/html;charset=utf-8" http-equiv="Content-Type">
  <TITLE>Background image testing</TITLE>
<BODY background="image.jpg" style="margin:0">
<iframe src="IFrame.htm"
style="width:100%;height:100%;FILTER:chroma(color=#FFFFFF)" frameborder=0>

IFrame.htm for Bug 1:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
<title>Iframe holder</title>
<FRAMESET frameBorder="0" bordercolor=red border="10" cols="30%,*" framespacing=1>
    <FRAMESET frameBorder="0" bordercolor=blue border="20" rows="*,*"
        <FRAME frameBorder="1" bordercolor=green
bgcolor=yellow><div>This is the easel</div></body></html>'">

IFrame.htm for bug 2A-1:
change frameBorder="0" to frameBorder="1" in the two <FRAMESET ...> tags
(now all the borders will be green)

IFrame.htm for bug 2A-2:
now move borderColor=green to the second <FRAME ...> element (and remove it from
the first one).
(now all the borders will be blue)

IFrame.htm for bug 2B:
Change the border attribute in the two <FRAMESET ...> elements to border=1
(now we get thin 1px black lines for the borders)

IFrame.htm for bug 2C:
Add a frameBorder=0 attribute to the 2nd and 3rd <FRAME ...> elements
(nothing changes)

Note that similar comments to those in apply here
about some extra part in the files so that IE will work.
The resizing issue is known (and has a bug filed on it).

The coloring issue is probably a non-issue in current builds, but I'd need a
testcase to check.  Please attach one using

Comment 2

13 years ago
Created attachment 176505 [details]
iframe for 2nd testcase

reporters iframe for bug 2a-1

Comment 3

13 years ago
Created attachment 176506 [details]
reporters testcase 2a-1

  <META content="text/html;charset=utf-8" http-equiv="Content-Type">
  <TITLE>284255 Background image testing</TITLE>
<BODY background=""
<iframe src=""
style="width:100%;height:100%;FILTER:chroma(color=#FFFFFF)" frameborder=0>
Over to frames for the color issue (which is still there).  Helpwanted.
Assignee: roc → nobody
Component: Layout: View Rendering → Layout: HTML Frames
Keywords: helpwanted
QA Contact: ian → layout.html-frames
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:

Comment 6

13 years ago
I'm confirming that this problem still exists on my Win XP Pro with Deer Park
Alpha 2 downloaded yesterday: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.9a1) Gecko/20051007 Firefox/1.6a1


13 years ago
You need to log in before you can comment on or make changes to this bug.