Closed Bug 307136 Opened 19 years ago Closed 19 years ago

expands DIV's area using mouse events doesn't work when over IFRAME tag

Categories

(Firefox :: General, defect)

Product:
Firefox
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: viniciuscamara, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.7.10) Gecko/20050717 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; pt-BR; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

Using event onmouseover on the div tag to resize the div area.
But when continue pass the mouse over iframe tag, the event mouseover will be
lost. I don't have problems using IE.





Reproducible: Always

Steps to Reproduce:
1. Pass the mouse over the div
2. Div expands your area to another size when the mouse continue over the div
3. When the mouse out the div, your area returns to original size
Actual Results:  
The div's area returns to original size when the mouse stay over iframe tag.

Expected Results:  
Expected don't lost the event mouseover when pass the mouse over iframe tag

See the code bellow: 

<html>
<head>
<style type="text/css">
   #floatframe {
       position:absolute;
       left: 0px;
       top: 0px;
       background-color:red;
       width: 200px;
       height: 250px;
       z-index:1;
   }
 
</style>
</head>
<html>
<body topmargin="0" leftmargin="0" style="z-index:1">
<div id="floatframe"
onmouseover="this.style.width='450px';this.style.height='450px';"
onmouseout="this.style.width='200px';this.style.height='250px';">
asdfasdfasdfasdf
</div>

<iframe name="teste" style="display:block; BORDER-RIGHT: black thin solid;
BORDER-TOP: black thin solid; Z-INDEX: 0; BORDER-LEFT: black thin solid; WIDTH:
50%; BORDER-BOTTOM: black thin solid; POSITION: absolute; HEIGHT: 50%;
BACKGROUND-COLOR: transparent; TOP:250" SRC="http://www.google.com.br"
frameborder="1"></iframe>
</body>
</html>
Please test using the latest nightly trunk build.
I think it should work in that build.
http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/
(In reply to comment #1)
> Please test using the latest nightly trunk build.
> I think it should work in that build.
> http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/

Thankx a lot.
I will try to download file and report if the bug continue.
This bug will be correct in another product version?

(In reply to comment #2)
> (In reply to comment #1)
> > Please test using the latest nightly trunk build.
> > I think it should work in that build.
> > http://ftp.scarlet.be/pub/mozilla.org/firefox/nightly/latest-trunk/
> 
> Thankx a lot.
> I will try to download file and report if the bug continue.
> This bug will be correct in another product version?
> 
So, I made the download of the file "firefox-1.6a1.en-US.win32.installer.exe"
(Deer Park Alpha 2) and this bug not appear again.

Now I've some question about the product versions. See bellow:
Will this bug be correct in another product version? 
How long time to press another product version?

I need to know because my company will be developing using the Mozilla like web
browser default.

Congratulations to fix this bug.
Waiting your answers.
Thankx again.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
Status: VERIFIED → UNCONFIRMED
Resolution: FIXED → ---
WFM since we don't know what specific patch fixed this.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
(In reply to comment #3)
> Now I've some question about the product versions. See bellow:
> Will this bug be correct in another product version? 
> How long time to press another product version?
> 
> I need to know because my company will be developing using the Mozilla like web
> browser default.
Yes, the bug will not be there anymore in the next product version, Firefox1.5,
SeaMonkey1.0.
I don't know when that version will come out. Probably before this year, I
guess. Maybe somewhere in november, I hope.
(In reply to comment #5)
> (In reply to comment #3)
> > Now I've some question about the product versions. See bellow:
> > Will this bug be correct in another product version? 
> > How long time to press another product version?
> > 
> > I need to know because my company will be developing using the Mozilla like web
> > browser default.
> Yes, the bug will not be there anymore in the next product version, Firefox1.5,
> SeaMonkey1.0.
> I don't know when that version will come out. Probably before this year, I
> guess. Maybe somewhere in november, I hope.

So, many thanks and I'll wait the version come out!
If I'll find new bugs, I'll be back.
See U!
You need to log in before you can comment on or make changes to this bug.