thanks for the reply...Iīm looking at it on google 12 and the buttons are blue instead of black and the window opens behind!!
If you navigate away from the webpage and then return you may see that it has changed....I donīt know why but thatīs what I did and then it stayed wrong....I have a friend and a cousin seeing the same as me on different computers....so Iīm not halucinating...ha ha
I surfed from your site to CNN and this site and back to your site using the back button, but it still functions OK here. Also, your CSS seems in order - no blue(ish) colour anywhere to be found, so that would baffle me.
Regarding the opening behind graphics, try the following: in widget.css:
margin: 0; /* as is */
padding: 0; /* as is */
z-index: 999; /* did not see a z-index declaration here */
/* from here on: if the background and z-index are no cure */
margin-left: -240px; /* half the iframe's width */
height: 570px; /* same */
Thanks again for the reply...when I said the button is blue...I meant the text is showing up in blue... like a normal link (with no black background)
your code has improved the situation a lot!!! cheers
I used the top half of the code only!!
(the bottom half with the positioning didnīt work well in explorer or firefox) it opened 1 and a half windows....
so now everything is still ok in fiefox and explorer
In google chrome (the x īclose windowī button is missing in the pop up) and the buttons still appear as blue links , and the window pops up to the side but at least itīs possible to use it although it doesnīt look professional
Nope, things are still OK here, also in 1024x768. You can test different versions of Chrome and Safari through http://spoon.net/browsers/. Just make an account and the different versions open on your computer without being installed. Which browser versions are significantly used nowadays can be seen on http://gs.statcounter.com/. Be sure to select Browser version, your country and 'Bar'. (The erratic shape of the Chrome lines in 'Line' are caused by growing pains in Chrome browser sniffing.)
Which versions? Cos' we might be breaking our heads over something that is a browser version fault. Especially the earlier versions of Chrome had quite a number of bugs. That's why they are releasing new versions is such a high tempo.
I'm afraid I don't have time to dive in it any further. It does baffle me, because on two machines here things work out well in Chrome 12 and Saf 5, and you don't have problems in FF either. The only thing, regarding the knobs, I could suggest is to remove the ../ from the url that calls in the knob bg image, in widget.css.