I don't care about the javascript. I go to google 20 or 30 times a day and it's nice that I can just type and hit enter. If I really cared, I'd just add a google search box to my browser, I suppose, and save the trip to google in the first place. And I doubt having to click on the search box will cause anyone any grief at the mod_perl site.
I do think it's a bit much to argue that because some javascript is bad all
javascript is bad - people that think that way can just turn off javascript
in their client. I think we will find that the CSS stuff is probably less
supported than a simple focus() javascript bit. But I would support a
pop-up window saying we are a pop-up window free site.
ok, let's not argue about this and concentrate on more important thing. Let's simply try to use autofocus and if people complain we will remove it. Though I agree with Allan that we need to use named property, rather than numerical order
onLoad="document.search_form.query.focus()"
I do think standard form buttons are a bit big and ugly. If that search box is going to be on the same line as the other widgets I agree it would be nice to make it look the same.
Sorry if I missed something, but why not use <input type="image" ...> submit button? Wouldn't that make it possible to make the search form look more like the other links on that same line?
Because there are browser where using the image as a submit button, breaks the 'Enter to Submit' feature. Again if you think we want to give it a try, let's do it.
in that case we need a button which looks the same as the prev|next buttons. let's say that the query is white bg, so the search button should use the dark bg. Anybody?
There was also talk of having an option to limit the search to just that area of the document tree, which I've implemented on the search page, but we would need a way to pick the type of search on each page, too. That either means a checkbox, or a second submit button. Might be able to use two submit buttons as graphic images in a more attractive (less obtrusive) way than a real check box and a real submit form button.
I suggest to always use the current context for searching and to have no checkboxes on every page. And display all the options on the dedicated search page.
It may confuse a few people in first place, but if we clearly state on the results page that 'You have searched FOO section', followed by a search form with all the options in it, users will learn fast that if they want to have a global search they can do it from / or by going to the search page.
I'm +1 on this logic.
BTW -- is the larger fonts (and thus the wider search input field) on NS4
just a fact of life?
looks like it. you could try to reduce the fonts in the preference.
Oh, I just resized in NS4 and see that the site still falls apart -- that is all the text in the content section ends up in a single narrow long column. Was that decided that is also a fact of life? Maybe a solution there it so use javascript -- reload on resize?
To me now it's a fact of life. Our goal is to make the site look great in modern and/or properly implemented browsers and be usable in old and/or broken browsers. Currently NS4 is quite usable. It's definitely not pretty.
_____________________________________________________________________ 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]
