Having popup window difficulties - fixed sized popups...

Poster: aquaverse
Dated: Wednesday February 16 2005 - 15:27:32 GMT

I have implemented my menus and all is well except for one thing. Here's the site: http://www.icruise.com/. Here's the menu_data source code for opening these fixed sized windows:



The windows come up correctly in IE and Netscape, but are not fixed in Firefox. Can anyone help me correct the code?

Thanks in advance,

Geoff
icruise.com

Update: I used the information on this page to create the popup and it resulted in opening a different sized popup window in Firefox.
http://milonic.com/menusample11.php

Poster: John
Dated: Wednesday February 16 2005 - 16:53:56 GMT

Try...

Poster: aquaverse
Dated: Wednesday February 16 2005 - 18:20:03 GMT



Same result.

http://dev.icruise.com:10222/resEntry.j ... te=4/10/05

Under Cruise Categories, top link is your new one. Second link is my original. Any other suggestions to fix the window size in Firefox?

Thank you for looking into this...

Poster: John
Dated: Thursday February 17 2005 - 13:08:31 GMT

Your menu code placement is incorrect for using the menu inside a td. See http://www.milonic.com/tablemenu.php for instructions.

Poster: aquaverse
Dated: Thursday February 17 2005 - 14:20:37 GMT

Thanks for pointing that out, John.

I fixed that issue on this page:
http://dev.icruise.com:10222/search.jsp ... range=5000

However, the fixed-sized popup problem in Firefox still persists. Any other suggestions, or am I stuck with it this way?

Thanks.

Poster: aquaverse
Dated: Thursday February 17 2005 - 14:50:18 GMT

Also:

When I use the proper table structure for the menus as presented in the link above, my menus become noticeably slower. My boss wanted to use these menus because they are so fast, so this is yet another problem. Menus seem to work with incorrect syntax, though, so I may keep as is for now.

Poster: Ruth
Dated: Thursday February 17 2005 - 19:22:23 GMT

Is there a particular reason you have the menu in a table? From the layout it looks like you could set it up as absolute positioned?

Ruth

Poster: aquaverse
Dated: Friday February 18 2005 - 20:45:15 GMT

Yes, in another thread I mentioned that we have affiliates who add their own html to the tops of our pages, so depending on what their code is, the menus get pushed around. Thus, relative positioning.

Poster: Ruth
Dated: Friday February 18 2005 - 23:50:06 GMT

Hi,
Sorry, I didn't know about that issue. Do you have a page with the correct layout so we can see why the menu is slow? Putting it in a table shouldn't change how fast it is, it's the same amount of data. And, putting all the calls for the menu in one table cell can cause problems in some browsers.

Ruth

Poster: kevin3442
Dated: Thursday February 24 2005 - 6:07:02 GMT

Hi Geoff,

Hmmm... the syntax for the targetfeatures property is shown in sample11 the way John suggested you try it. But that apparently doesn't work. It's as if only the first attribute in the sequence is having any effect. So, I tried something else. It may seem odd, so let me explain why I tried it.

The menu's targetfeatures property essentially passes the specified values to the optional features (or attributes) parameter of javascript's native window.open() method. In the window.open() method, the features parameter is a comma-separated list of window attributes passed in a string. Since you would normally use a comma-separated list when calling window.open() directly, I figured it'd be worth a shot to try a comma-separated list (rather than space separated) in the menu's targetfeatures property. It worked! In other words, you might try:

Note the comma between with=415 and height=440.

Other things to note: (1) I also got rid of scrollbars=no because I believe "no" is the default state for scrollbars in a popup window. (2) Instead of target=_blank I used target=newWindow, just to give the window a name (in case you need to reference it later. _blank will do if you won't need to reference the open window for anything later). (3) I'm sure you know this, but it doesn't hurt to remind people... Since your window is a popup, your users may not see it if they have popups blocked.

Give the comma separation a shot and see if that works for you. If you'd rather not try it (given that it's not quite according to documentation), then you could always go with a js function to open your popup. If you don't know how, then we can show you if that's something you'd like to try.

Hope that helps,

Kevin