Inconsistent enter key behaviour

[cknowles]

The enter key seems to submit for some APIs but not others. Taking the pet store example:

• The first three POSTs use enter for a new line in the request body. This is understandable.
• "Updated user" PUT uses enter for submit. It's in the "/user" section.
• "Get user by user name" GET uses enter for submit. It's in the "/user" section.
• "Logs user into the system" GET doesn't seem to do anything on pressing enter. It's in the "/user" section.
• "Find pet by ID" GET uses enter for submit. It's in the "/pet" section.
• "Finds Pets by tags" GET uses enter for submit. It's in the "/pet" section.

I'm using the latest consumer version of Chrome 26.0.1410.64m and the current master with the petstore example at http://petstore.swagger.wordnik.com/api/api-docs.json.

[fehguy]

please reopen if still an issue

[cknowles]

Still an issue but I don't seem to have permissions to reopen.

[chaaban]

It Applies the api-key only when it change , so if u refresh the page and the key is here it wont be applied.

In index.html :

 $('#input_apiKey').change(function() {
      var key = $('#input_apiKey')[0].value;
      log("key: " + key);
      if(key && key.trim() != "") {
        log("added key " + key);
        window.authorizations.add("key", new ApiKeyAuthorization("API-KEY", key, "query"));
      }
    })

In my case , since I hard code the api-key for testing purpose , i just added

var key = $('#input_apiKey')[0].value;
window.authorizations.add("key", new ApiKeyAuthorization("API-KEY", key, "query"));

Inside the onComplete function of : window.swaggerUi

You can add a condition to test if there is a value inside the input and add the key if it's the case.

[fehguy]

@ponelat can you look at this please?