Thing is my customer, Bob From Marketing, wants a new feature. He knows "Text Input","Drop Down","Form","Button", "Checkbox" as terms to communicate his feature

Thing is my customer, Bob From Marketing, wants a new feature. He knows "Text Input","Drop Down","Form","Button", "Checkbox" as terms to communicate his feature to me. He knows this because he used to code some Visual Basic on the side when he was "still a programmer" all those years ago. Now in reality, I don't take any thing Bob tells me literally as directions. I treat it more as a description of Bobs problem. I then forget everything he told me he wanted and build the tool necessary to do the job he's described. "drop-down" works just fine thank you. It's adequately descriptive to support its most common application - which is communicating with non-technical people. But what about communicating with a technical person? Well, they're going to do what they want to/the sensible thing anyhow no matter what I call it.