Disappearing SUBMIT button on create account

[onelove5683]

Perhaps your HTML and CSS are fighting against each other and causing an overlap whereby the button is overlapped or shoved out of view because of insufficient space etc?
Does the disappearing happen when you resize your browser window wider and taller?
How about if you turn off the right and/or left column globally as a brief test?
How about if you change to the Classic template instead of your custom template?

• The button is not there after resizing he browser window.
• I turned off the right and then ledt columns globally and still no submit button. Even with both columns off at the same time.
• When I switched to the classic template, the button was there.

If the HTML and CSS are fighting against each other causing an overlap, why is it just happening in IE? And how do you recommend fixing the issue? Thanks.

[Kim]

^^^ See my post above.

[onelove5683]

^^^ See my post above.

I just checked it out. The issue with with IE7 though, it seems like the peekaboo bug is a problem with IE6, or both?

I tried to go to the CSS and uncomment the lines that mention the peekabo bug. Nothing changed, even after clearing cache etc etc.

How would I get the damn peekaboo bug anyway? There don't seem to be any other issues with the site in IE. I'm not convinced that this is the problem... I may be wrong though.

=/

[tvadpro]

^^^ See my post above.

I did precisely that Kim -- thank you for (probably) clearing up yet another one of my headaches. OneLove, you might be interested in this solution for the peek-a-boo. Have not yet implemented it, but I will be doing so in a few days. Author of the page linked above claims the peek-a-boo still manifests in IE7, and may even be WORSE than it was in IE6.

Also, I'm probably running the same Web-Stat code mentioned by Rob. Probably has nothing to do with the disappearance of my submit button -- just one category of issues I'll eventually need to fix for HTML validation.

As for OneLove's question about why the button misfires sometimes in IE but never in Firefox -- refer to my initial comments regarding W3C standards compliance and Microsoft's refusal to comply.

At the risk of saying so prematurely, thanks for helping sort this out, everyone.