Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris
 
PerlMonks  

comment on

( [id://3333]=superdoc: 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.


In reply to SuperSearch: hitting "return" in form with altered query by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (7)
As of 2024-04-25 11:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found