Playground UI bug: function "submit" button blocks the function return text field

API Bugs
1

Issue: While you are typing a function return to test the model, the typing goes right under the submit button.

A code editor shows a function call to with integer parameters, and the response humorously states that float values aren't allowed as parameters. (Captioned by AI)
A code editor shows a function call to with integer parameters, and the response humorously states that float values aren't allowed as parameters. (Captioned by AI)469×235 7.52 KB

To tell what was typed, one must lose focus of the input box.

Did I make a typo here, when I’m trying to manually return a value to the AI in the Prompts Playground (chat completions)? Can’t tell.

1 Like
2

Hi - I am unable to reproduce the issue in our test environment. Could you please describe the steps to reproduce (including the exact URL) and could you please indicate the browser and browser versions? Once I am able to reproduce the issue, I can file a defect with our Engineering team. Thank you.

1 Like
3

Developer customer API account, and prompts playground with a function.

Here is a preset with functions:

https://platform.openai.com/playground/prompts?preset=preset-8inCYbuAVpAXIu8trnEktGY0

Ask a question requiring a function call such as:

" Generate a random integer 1-100 "

Wait a terribly long time as the function builds a temporary context-free grammar.

Then you’ll receive the AI wanting to use a developer function:

The image shows a code assistant interface where the user asks to generate a random integer from 1 to 100, and the assistant responds with a code snippet using "rand_int" specifying "range_end: 100" and "range_start: 1". (Captioned by AI)
The image shows a code assistant interface where the user asks to generate a random integer from 1 to 100, and the assistant responds with a code snippet using "rand_int" specifying "range_end: 100" and "range_start: 1". (Captioned by AI)400×352 8.57 KB

Then you simulate text being returned by typing into the response text field. While typing there is a submit button, and your text cannot be seen after growing long enough:

A user asks the assistant to generate a random integer between 1 and 100, and the assistant responds with a code snippet using "rand_int" specifying the range_start as 1 and the range_end as 100. (Captioned by AI)
A user asks the assistant to generate a random integer between 1 and 100, and the assistant responds with a code snippet using "rand_int" specifying the range_start as 1 and the range_end as 100. (Captioned by AI)406×342 9.76 KB

The original report was seen in the Firefox browser, and in these pictures I replicated it on Chrome, indicating the issue’s breadth. It happens at every browser width where the text would be long enough to reach and go under the button.

4

Thank you. I have tested and can see the reported issue. Please note, that the test does overflow as you keep typing, however, I understand a a UI improvement could be implemented. I will escalate this feedback to the respective team.