At 09:55 PM 03/06/02 +0800, allan wrote:
Stas just mentioned about using pure-text for widgets. This is fine, but we would want everything to match up, right? That is prev|up|next as text, too.
Frankly, I think graphics are our best bet for consistent design, but someone running at 140dpi will complain (duh, of course it looks small). If it was me, I'd probably wrap the entire widget row in a table to keep them all aligned, but maybe that's not necessary.
Yes, we will go with images. And no 140dpi shouldn't be a problem, since you should figure out once what the functionality of these images. after that they can be blank and you will still know what they do ;)
BTW - Stas, why were the hidden fields in a different template -- which required placing the </form> tag there, too? I moved everything into the "search" template and it seems to work fine.
For fun, I just used a very simple "search" template and generated this:
http://hank.org:5000/about/about.html
From looking at the source, you've lost 3 hidden input vars. Anyway I'll try moving these again.
Now, if you use IE5.5 or IE6.0 you can see the thin border I was talking about with
http://hank.org:5000/about/about2.html
Which ends up a lot like the prev|up|next widgets (although I used a different font for the "search" button. But, it's hacked up to work in IE (just as an example!).
Of course, it doesn't work as well in other browsers, as very few seem to apply the style to the input field. Opera applies it, but differently. Most seem to make the input box *larger*, so maybe that's my misuse of the style tag. What happens is that the input box and submit button are out of proportion.
The current CVS solves that by wrapping the input field and search button in a table with the dark border, but then although the input field/submit button makes a more unified "search" widget, it doesn't match as well with the other widgets on that same line as the large input field.
And that style on the input field totally trashes NS4 for some reason. Not sure if there's a work-around other than @import.
;(
Is "certain browser" NS4? Technically we can use an image as a button as a
submit, but are you saying you can't create the exact same look and have it
work?
for NS4 not possible _lookwise_. ns4 thinks the image is a link and then puts an unremovable (if we want legal html) border around the image.
Actually, the blue border doesn't look that bad in NS4 (and NS6).
http://hank.org:5000/about/about3.html
Now, the oversized text input field is another story, not to mention the resizing problem. So the blue border would be down the list of NS bummers. From talking to people the oversized input field is just life.
[out of order quoting]
ok
so all in all this solution is only going to look slightly worse in ns4, because of the link-border but will function everywhere one way or the other i guess.
If we use the illegal border="0" I don't think the W3C police will really come after us. Will they?
we better not I think.
functionality-wise it seems some browsers on some platform doesn't understand the enter-key when this is applied but as jonathan pointed out people will figure out how to click on the image if suddenly their enter-key doesn't work.
I have:
Win98: IE6, Opera6.01, Mozilla0.9.7, NS4.08 WinME: IE5.5, NS6 Linux: Mozilla0.9.7 Konquerer2.2.2
All work with the enter key.
good!
_____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
