Archive feature request (very small nag).
Hello and hi there!
1. Add to ToDo list*:
When user clicks "Search" place cursor automatically in the "Search expression" box.
Along those lines:
2. Add to ToDo list*:
When user clicks "Advanced Search" place cursor automatically in the top "Title" box.
Thank you ;-)
*Please and pretty please.
1. Add to ToDo list*:
When user clicks "Search" place cursor automatically in the "Search expression" box.
Along those lines:
2. Add to ToDo list*:
When user clicks "Advanced Search" place cursor automatically in the top "Title" box.
Thank you ;-)
*Please and pretty please.
Post edited by ZnorXman on
Comments
That would mean the page scrolls to the bottom to focus every time you open the Archive! page.
Every other link to search (e.g. the one on the main page) does the requested auto-focus, though.
Good call, and now done (turned off with the same config option.)
So do the autofocus only if the #search anchor is present in the URL.
Thank you, that's kind of what I was getting at, i.e. place the cursor AFTER clicking http://www.worldofspectrum.org/archive.html#search and not at immediate load-up of the page.
Thanks!
:-)
Okay, but since it's a static page, that would require Javascript.
It can probably be done in Javascript, but that feels wrong (having to turn the focus on or off by turning Javascript on or off is counter-intuitive to the otherwise used infoseekconfig tool).
How about removing that search form from the Archive! page and making the #search link at the top go straight to infoseek.cgi like all other search links on the site? It would be more consistent.
Gets my thumbs up.
It's a logical step to take with minimal fuss.
"Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
EDIT below ... sorry spelank miztuk.
[strike]and also :
"Not Found
The requested URL /archive.htm was not found on this server.
Additionally, a 503 Service Temporarily Unavailable error was encountered while trying to use an ErrorDocument to handle the request."[/strike]
Whew! That's ok then ... the other one would have been worse ... "capacity problems" :grin: