From what I can see just by viewing it in Seamonkey and looking at the contents of the page and your CSS, you may want to check the style for the div that the button is contained in. I can see the button in Seamoney, but it is cut off at the very top, only allowing about 1-3 pixels to show. I can click it as well My guess would be that since you are setting a static height of 34px for the style that is applied to the parent div of the button, it is cutting off most of the button.
From what I can see just by viewing it in Seamonkey and looking at the contents of the page and your CSS, you may want to check the style for the div that the button is contained in. I can see the button in Seamoney, but it is cut off at the very top, only allowing about 1-3 pixels to show. I can click it as well.My guess would be that since you are setting a static height of 34px for the style that is applied to the parent div of the button, it is cutting off most of the button.
Also I have changed the 34pc to 64 and that made no difference in the button showing up or being clickable. :( – Abs Jan 31 '09 at 21:51 I just installed seamonkey (1.1.14) and its the same as Firefox 2! – Abs Jan 31 '09 at 21:55 Yes, it was cutting the button of due to the small height.
– Abs Jan 31 '09 at 22:08.
I observe the same behavior as s13james (+1 for that) but have some more things I want to point out. You may want to rethink your use of line-height and height there, as the wrapping of that input element to the next line with the combination of those values has a lot to do with your trouble. I see you're applying the same style via id and class, however that style is declared only for use as a class: div.
W_span_auto{ background:url(../images/wr. Png) top right no-repeat; padding-right:18px; height:34px; line-height:34px; text-align:left; border:none; } (For an id, you'd need to have declared it as div#w_span_auto. ) I'm not sure why you're declaring it twice either.
There's an identical declaration later in the same css file. Cheers.
It also only has a 3% market share: marketshare.hitslink.com/report.aspx?qpr....
It is enabled and lol yes, a few ppl complained :) – Abs Jan 31 '09 at 21:46 You are a better man than I sir. – Dave Markle Jan 31 '09 at 23:51.
No, I don't want my form to be submitted. I am making use of AJAX that does that for me via a GET request. – Abs Jan 31 '09 at 21:47 @Abs, You can hook the submit button to a function which does your Ajax mojo, and returns false.
Thus, the form won't be submitted with Javascript enabled, but it will when it is disabled. Great option for accessibility. – strager Jan 31 '09 at 21:54 Ah I see, I think I achieve the same thing with just the button.
I am not sure if I achieve accessibility though? – Abs Jan 31 '09 at 22:08.
I have a site that has a simple HTML button in a form. All browsers show this button correctly. However, in Firefox 2 and Seamonkey it appears just as a solid grey square that cannot be clicked on and that has no text.
No idea why but what I did was increase the size of the div holding the button so that the button can be shown fully. There wasn't enough space for the button to be clicked. Firefox 2 and Seamonkey managed to find this a bit troublesome.
Thank you all for your help.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.