The "Freeola Customer Forum" forum, which includes Retro Game Reviews, has been archived and is now read-only. You cannot post here or create a new thread or review on this forum.
If you look at it in Firefox/Moz/Decent browsers you get a great thumbs up, but in IE it's a massive thumbs down. The menu on the right is a div and the main text is also a div. When I remove absolute positioning on the main div it seems to work fine, so I think the nested divs or left-most div is causing some problems. Can anyone shed any light on this? Thanks!
IE be damned! Even my phone renders it properly heh.
EDIT: Those inputs look like they're aligned right, they're not, it's a coincidence. The label span seems to be sized 50% between the #main div, and formw span seems to be sized 50% from the whole page.
> Becuase it's true? :-)
Although the aim is pure CSS eventually, I've slowly discovered, that in some cases, it hinders accessibility, especially in the use of forms.
Part of me still sees a form as tabular data, and as long as you have included tabindex's, accesskeys, summary's, labels and titles, I see no reason not to continue using tables for retaining the layoutof forms.
Also, although degredation is acceptable for appearence in CSS based sites, and that you can also pull of some clever "alternate" (read: crap) browser support, form styling in CSS is still a bit hit and miss if CSS is disabled.
FWIW, why are you using when you should be using
> FWIW, why are you using when you
> should be using
http://www.endeavourchem.co.uk/search.asp
Before anyone starts slating it, it's no where near finished, the homepage doesn't work for a reason, The menu system is based on the ALA Suckerfish style and the reason the true homepage isnot there is I'm using the server for testing the ret of the site due to needing a reference to / for everything (which doesn't work locally on IIS6!!)
I've got a few designs to share in a week or so.
> Before anyone starts slating it ...
Nothing to slate, but the submit and reset buttons are hidden behind the footer. Just thought I'd let you know in case you've got a 1024 x 768 screen res and hadn't checked an 800 x 600.
Also, again nothing to slate, but would it not be better to have the reset button to the right of the submit, and not the left? As I can invision people hitting the tab and enter button after entering their last piece of text, and finding there filled in form is empty.
Or perhaps remove the reset button altogether. It'll stop anybody from hitting it by mistake, and I don't think it is used all that muchthese days anywhere (when was the last time you used one).
I like the header image, and the drop-down works great (aside form the horizontal pop-up of the nav bar). Was it for this site you were asking about the suckerfish stuff on DO?
> Also, again nothing to slate, but would it not be better to have the
> reset button to the right of the submit, and not the left? As I can
> invision people hitting the tab and enter button after entering their
> last piece of text, and finding there filled in form is empty.
>
> Or perhaps remove the reset button altogether. It'll stop anybody
> from hitting it by mistake, and I don't think it is used all that
> muchthese days anywhere (when was the last time you used one).
Somthing I've alway had trouble with is button order.and in theory all you need is submit, but then are you removing and accessible option by taking away reset? Tabindexing, I've always placed the button in that order with a tab index making submit first, but your right about natural tabbing.
Gives me something to do at work tomorrow.
FWIW, only time I use reset is for credit card details.
> I like the header image, and the drop-down works great (aside form
> the horizontal pop-up of the nav bar). Was it for this site you were
> asking about the suckerfish stuff on DO?
My suckerfish is a mess. Must have been elsewhere when i coded it due to so many missing closing tags! Try validating it... Blonde moment there!;)
Funny moment today. A firm one of my clients used to work for i sbeing sued for breach of copyright based on the tabbing and white space in the Javascript!
Almost died laughing
Thanks Alan, I'll give that a shot. When I wrote that markup I wasn't aware of
:-)
(You even got a closed input tag there... jesus what have I become...)
> Gives me something to do at work tomorrow.
I suppose for those with JavaScript enabled you could add an 'Are you sure you want to clear the whole form' confirm box before letting the data be wiped.
> Funny moment today. A firm one of my clients used to work for is
> being sued for breach of copyright based on the tabbing and white
> space in the Javascript!
Did I read that right? Someone is claiming they own a copyright on the way they've written some JavaScript?
I used to see that a lot on web sites, a 2-line piece of code to redirect out of frames with 10 lines of copyright.
> When I wrote that markup I wasn't aware of
Next up is the fieldset then (unless you know about those too).
Unless it's an odd mark-up idea, that is offered as open source, as long as there is credit given...
Ugh. I hate CC.