On Tue, Jun 30, 2009 at 05:57:19PM +0100, Nick Fitzsimons wrote: > Bear in mind that some browsers, especially on non-Windows platforms, > have file inputs that don't look anything like you're probably > expecting - i.e. they aren't a text input field with a button next to > it.
The examples on the pages you linked were pretty much what I was expecting. The Safari example you pointed out didn't really differ in any substantial way, it just doesn't draw a recessed box around the area where the selected filename is displayed. > That's the way it was implemented in the earliest browsers to > support forms (early '90s), but there's no reason why it has to be > that way. Indeed. All the more reason to make use of the browser's default behaviour rather than forcing a non-standard appearance onto it and violating the user's expectations for that OS/browser combination. > I think it's probably going to > have a lot of white space around its two components... Much better, IMO, to have a lot of whitespace around the two components than a 750px wide column containing: input type=text at 100% width making it 725px or so wide_______________ input type=file* input type=text at 100% width making it 725px or so wide_______________ * Also 100% width, but displayed as if it were the default size, scrunched up against the margin despite this. (And, yes, I realize that arguments could be made that perhaps making the type=text inputs 100% width and letting them be 725px wide is a bad idea in the first place, but that's a design discussion and I asked a technical question, not a design question.) -- Dave Sherohman ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
