Thanks :). I plan to stay a while. Developing a personal website now. Getting back into the groove of things. Rubiks cubes is getting slightly boring. I’m not progressing much anymore. My finger speed is limiting me :(.
Alternatively, you could also float both the texarea and the input right and give the form (or the containing element within the form, as both should be wrapped in a block element in order to validate) overflow:hidden;
Yes, if you float them both to the right, the visual order will change without altering the HTML. But it’s a little odd to have the submit button to the left. At least in ‘left-to-right’ cultures, that’s not very intuitive.
Exactly, although it will also (in the case of a blank document with only this stuff) it will cause it to be all the way over on the other side of the parent, in this case, the other side of the browser.
I agree it’s not good UI for Western cultures. I was just trying to say it can bed done w/o messing the source order. It is , after all, more semantic for the submit button to come AFTER the textfield in the source , no matter what culture.
I also wonder if our western mindset might be at issue here. Maybe the whole thing would be fine with: form {direction:rtl;}
(also see that’s not the issue… blah)
Simplest solution EVER, as both elements are inline ( am assuming you want the submit button aligned to the top of the text area): textarea {vertical-align: top} and that’s it.
Well if the submit button is first, then that also means the tab order is screwed up. The submit button will be first in the tab order and THEN the textarea, unless of course you set hte tab index.
I don’t think our culture is to blame, unless you intend to blame the direction we read things in