Modal Window bug

[darkyndy]

URL: http://www.embevi.com/home
Browser(s) used: FireFox 3.5 [Mozilla/5.0 (Windows; U; Windows NT 6.1;
en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729)]
Location: Romania

Issue: I've added Friend Connect Bar and you can do this steps to
reproduce the bug:
Step1: Click on "Members" or "Comments";
Step2: Click on the "Undock button";
Actual result: the modal box has height = browser visible area height;
Expected result: Modal box should have height = HTML>Body height;

This issues doesn't look good if you scroll the page and you see from
the modal box that gray background and after that normal background
color.

Also if you can add a link on Google Friend Connect page that will say
"Found a bug?" Because it took me a lot of time to find where to post.

I write this message because I posted at
http://www.google.com/support/forum/p/friendconnect/thread?tid=6c56e0a0b05de73d&hl=en
and I was pointed here.

Best regards,
Paul

[Bob Aman]

> Actual result: the modal box has height = browser visible area height;
> Expected result: Modal box should have height = HTML>Body height;

Sorry I didn't answer this sooner. I could not duplicate with either
FireFox 3.5 or Chrome. Does this happen for you on any other browser?

-Bob

[Bob Aman]

> I've wrote there steps to reproduce... did you do those steps and you cannot
> reproduce?

I followed your steps exactly and could not reproduce. However, now
that I've seen the screenshot, try this in your CSS:

.modal-dialog-bg {
height: 100%;
}

-Bob

[darkyndy]

With FireBug I've tried this in first place, when I've posted this
bug, the problem is that the height is rewritten by Friend Connect
Script, I think when you scroll. :)

[Bob Aman]

> With FireBug I've tried this in first place, when I've posted this
> bug, the problem is that the height is rewritten by Friend Connect
> Script, I think when you scroll. :)

Probably true. Try this instead then:

.modal-dialog-bg {
height: 100% !important;
}

That won't work in IE6, but at the very least I think it should fix it
in the more modern browsers. I'm working on getting a permanent fix
that won't require this work-around.

-Bob