Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

SuperSearch: hitting "return" in form with altered query

by LanX (Saint)
on Oct 09, 2014 at 17:02 UTC ( [id://1103321]=monkdiscuss: print w/replies, xml ) Need Help??

After a partial search in SuperSearch hitting return seems to be bound to the first submit button

<input type="submit" value="Next >" name="nx">

Unfortunately that means altering the query doesn't restart at the beginning of the DB after hitting return but continuing where the last query stopped.

So it's necessary to click

New <input type="submit" value="Search" name="go">

explicitly.

I can't see an application for binding the return-key to "Next >" while it's handy after altering a form entry.¹

My suggestion would be to add a hidden

<input type="submit" value="Search" name="go" style="display:none">

prior to

<input type="submit" value="Next >" name="nx">

to change the default for return-key.

This SO discussion shows different ways to do so how-to-submit-a-form-when-the-return-key-is-pressed

I haven't tested yet...but I think we have enough HTML expertise in this board to find a solution! :)

Cheers Rolf

(addicted to the Perl Programming Language and ☆☆☆☆ :)

¹) for creating a keyboard submit you need to select a form element. The only way to select "next >" w/o clicking is to hit the "tab"-key. But in that case pressing "bar"-key has still the effect to continue the search.

All other form elements should be bound to "Search" again.

Replies are listed 'Best First'.
Re: SuperSearch: hitting "return" in form with altered query
by Anonymous Monk on Oct 09, 2014 at 23:58 UTC

    After a partial search in SuperSearch hitting return seems to be bound to the first submit button

    Yeah, the "starting at year month date" portion seems to be carried over... I don't think html is the solution :)(javascript maybe)

      > the "starting at year month date" portion seems to be carried over

      Obviously the "Next >" button needs that!

      It just doesn't make much sense to trigger a "next"-submit with "return"-key, cause the natural place to use return is within the form.

      But nobody ever edits the form if he just wants the next results of the unaltered form.

      Of course one could use JS, but it's not really needed, at least in FF.

      Cheers Rolf

      (addicted to the Perl Programming Language and ☆☆☆☆ :)

Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Node Status?
node history
Node Type: monkdiscuss [id://1103321]
Approved by sweetblood
help
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others musing on the Monastery: (7)
As of 2024-04-23 18:49 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found